17 extractive question-and-answer pairs built from TLC Trip Record Data - TLC, published by nyc.gov. Every answer is a verbatim span of text the source prints, and each row carries the passage it sits in, its offset in that passage, the source quote, the page and the location in the document, so any row can be checked against the original. 12 of the 17 pairs (70.6%) are explanatory questions and 5 restate a figure. 100.00% of rows pass the corpus quality gate.
Use the API URL with your free DD token in notebooks, scripts, and pipelines.
https://www.desidata.in/api/datasets/tlc-trip-record-data-question-and-answer-dataset/downloadDataset downloads are free. For Python or API downloads, sign in once and create a free DD token; set it as DD_TOKEN or save it in your notebook's secrets. Requests are linked to your account so your download history and counts stay accurate.
# One-time install: pip install desidata
# Set DD_TOKEN in your environment first (create a free token in Profile & settings).
import desidata
df = desidata.load("tlc-trip-record-data-question-and-answer-dataset")
df.head()Sign in with Google to download.
Usable for analysis, but expect some cleaning before you rely on it.
Annual Report 2015-16 by agriwelfare.gov.in - Question and Answer Dataset
Economy · 1,013 rows
Higher Education in India - Question and Answer Dataset
Economy · 1,594 rows
Gender Policy of NABARD - Question and Answer Dataset
Economy · 14 rows
ICAR Annual Report 2025-26 - Question and Answer Dataset
Economy · 1,101 rows
First 10 of 17 rows
| question | answer | context | answer_start | question_type | knowledge_quality_score | source_quote | source_page | source_location | confidence | validation_status |
|---|---|---|---|---|---|---|---|---|---|---|
| What was the reason TLC gave smaller bases more time to submit trip records? | Due to COVID-19 and its impact on the daily operations of small businesses | Due to COVID-19 and its impact on the daily operations of small businesses, TLC granted smaller bases an extension on trip record submissions. Trip and trip-related data for these bases will be updated as it becomes available. January February March April May June July August September October November December | 0 | relationship | 0.970 | Due to COVID-19 and its impact on the daily operations of small businesses, TLC granted smaller bases an extension on trip record submissions. | p[80] | 0.700 | valid | |
| Why did TLC grant smaller bases an extension on trip record submissions? | Due to COVID-19 and its impact on the daily operations of small businesses | Due to COVID-19 and its impact on the daily operations of small businesses, TLC granted smaller bases an extension on trip record submissions. Trip and trip-related data for these bases will be updated as it becomes available. January February March April May June July August September October November December | 0 | relationship | 0.970 | Due to COVID-19 and its impact on the daily operations of small businesses, TLC granted smaller bases an extension on trip record submissions. | p[80] | 0.700 | valid | |
| What actions does the TLC take to ensure complete and accurate trip record information? | routine reviews of the records and takes enforcement actions | The TLC performs routine reviews of the records and takes enforcement actions when necessary to ensure, to the extent possible, complete and accurate information. Since 2019 high volume trip records (HVFHV) are reported in a separate (and more detailed) dataset. For 2025 data onwards, a cbd_congestion_fee column has been added to the Yellow, Green, and High Volume FHV datasets to reflect new congestion pricing charges. Trip data is published monthly on this website, typically with a two-month delay to allow time for full vendor submissions. Due to the size of the datasets, the trip record files have been stored in the PARQUET format. Please see the ‘Working With PARQUET Format’ under the Data Dictionaries and MetaData section for details. Please be advised that there may be minor changes in the near future to standardize the parquet schema across all years and datasets. | 17 | relationship | 0.970 | The TLC performs routine reviews of the records and takes enforcement actions when necessary to ensure, to the extent possible, complete and accurate information. | p[1] | |||
| Why is there typically a two-month delay in publishing trip data? | to allow time for full vendor submissions. | The TLC performs routine reviews of the records and takes enforcement actions when necessary to ensure, to the extent possible, complete and accurate information. Since 2019 high volume trip records (HVFHV) are reported in a separate (and more detailed) dataset. For 2025 data onwards, a cbd_congestion_fee column has been added to the Yellow, Green, and High Volume FHV datasets to reflect new congestion pricing charges. Trip data is published monthly on this website, typically with a two-month delay to allow time for full vendor submissions. Due to the size of the datasets, the trip record files have been stored in the PARQUET format. Please see the ‘Working With PARQUET Format’ under the Data Dictionaries and MetaData section for details. Please be advised that there may be minor changes in the near future to standardize the parquet schema across all years and datasets. | 504 | relationship | 0.970 | Trip data is published monthly on this website, typically with a two-month delay to allow time for full vendor submissions. Due to the size of the datasets, the trip record files have been stored in the PARQUET format. | p[1] | |||
| What updates are planned for the PARQUET schema in the future? | minor changes in the near future to standardize the parquet schema across all years and datasets | The TLC performs routine reviews of the records and takes enforcement actions when necessary to ensure, to the extent possible, complete and accurate information. Since 2019 high volume trip records (HVFHV) are reported in a separate (and more detailed) dataset. For 2025 data onwards, a cbd_congestion_fee column has been added to the Yellow, Green, and High Volume FHV datasets to reflect new congestion pricing charges. Trip data is published monthly on this website, typically with a two-month delay to allow time for full vendor submissions. Due to the size of the datasets, the trip record files have been stored in the PARQUET format. Please see the ‘Working With PARQUET Format’ under the Data Dictionaries and MetaData section for details. Please be advised that there may be minor changes in the near future to standardize the parquet schema across all years and datasets. | 785 | summary | 0.970 | Please be advised that there may be minor changes in the near future to standardize the parquet schema across all years and datasets. | p[1] | 0.700 | ||
| What does the TLC state about the accuracy of the trip data? | TLC makes no representations as to the accuracy of these data. | Yellow and green taxi trip records include fields capturing pickup and drop-off dates/times, pickup and drop-off locations, trip distances, itemized fares, rate types, payment types, and driver-reported passenger counts. The data used in the attached datasets were collected and provided to the NYC Taxi and Limousine Commission (TLC) by technology providers authorized under the Taxicab & Livery Passenger Enhancement Programs (TPEP/LPEP). The trip data was not created by the TLC, and TLC makes no representations as to the accuracy of these data. For-Hire Vehicle (“FHV”) trip records include fields capturing the dispatching base license number and the pickup date, time, and taxi zone location ID (shape file below).These records are generated from the FHV Trip Record submissions made by bases, so we cannot guarantee or confirm their accuracy or completeness. | 487 | summary | 0.970 | The trip data was not created by the TLC, and TLC makes no representations as to the accuracy of these data. For-Hire Vehicle (“FHV”) trip records include fields capturing the dispatching base license number and the pickup date, time, and taxi zone location ID (shape file below).These records are generated from the FHV Trip Record submissions made by bases, so we cannot guarantee or confirm their accuracy or completeness. | ||||
| What might change in the near future regarding the PARQUET schema? | minor changes in the near future to standardize the parquet schema across all years and datasets. | The TLC performs routine reviews of the records and takes enforcement actions when necessary to ensure, to the extent possible, complete and accurate information. Since 2019 high volume trip records (HVFHV) are reported in a separate (and more detailed) dataset. For 2025 data onwards, a cbd_congestion_fee column has been added to the Yellow, Green, and High Volume FHV datasets to reflect new congestion pricing charges. Trip data is published monthly on this website, typically with a two-month delay to allow time for full vendor submissions. Due to the size of the datasets, the trip record files have been stored in the PARQUET format. Please see the ‘Working With PARQUET Format’ under the Data Dictionaries and MetaData section for details. Please be advised that there may be minor changes in the near future to standardize the parquet schema across all years and datasets. | 785 | summary | 0.970 | Please be advised that there may be minor changes in the near future to standardize the parquet schema across all years and datasets. | p[1] | 0.700 | ||
| What will happen to trip-related data for smaller bases? | will be updated as it becomes available. | Due to COVID-19 and its impact on the daily operations of small businesses, TLC granted smaller bases an extension on trip record submissions. Trip and trip-related data for these bases will be updated as it becomes available. January February March April May June July August September October November December | 186 | summary | 0.970 | Trip and trip-related data for these bases will be updated as it becomes available. January February March April May June July August September October November December | p[80] | 0.700 | valid | |
| Which datasets include the new column added for congestion pricing charges? | Yellow, Green, and High Volume FHV datasets | The TLC performs routine reviews of the records and takes enforcement actions when necessary to ensure, to the extent possible, complete and accurate information. Since 2019 high volume trip records (HVFHV) are reported in a separate (and more detailed) dataset. For 2025 data onwards, a cbd_congestion_fee column has been added to the Yellow, Green, and High Volume FHV datasets to reflect new congestion pricing charges. Trip data is published monthly on this website, typically with a two-month delay to allow time for full vendor submissions. Due to the size of the datasets, the trip record files have been stored in the PARQUET format. Please see the ‘Working With PARQUET Format’ under the Data Dictionaries and MetaData section for details. Please be advised that there may be minor changes in the near future to standardize the parquet schema across all years and datasets. | 336 | list | 0.820 | For 2025 data onwards, a cbd_congestion_fee column has been added to the Yellow, Green, and High Volume FHV datasets to reflect new congestion pricing charges. | p[1] | 0.700 | ||
| What fields are included in yellow and green taxi trip records? | pickup and drop-off dates/times, pickup and drop-off locations, trip distances, itemized fares, rate types, payment types, and driver-reported passenger counts. | Yellow and green taxi trip records include fields capturing pickup and drop-off dates/times, pickup and drop-off locations, trip distances, itemized fares, rate types, payment types, and driver-reported passenger counts. The data used in the attached datasets were collected and provided to the NYC Taxi and Limousine Commission (TLC) by technology providers authorized under the Taxicab & Livery Passenger Enhancement Programs (TPEP/LPEP). The trip data was not created by the TLC, and TLC makes no representations as to the accuracy of these data. For-Hire Vehicle (“FHV”) trip records include fields capturing the dispatching base license number and the pickup date, time, and taxi zone location ID (shape file below).These records are generated from the FHV Trip Record submissions made by bases, so we cannot guarantee or confirm their accuracy or completeness. | 60 | list | 0.820 | Yellow and green taxi trip records include fields capturing pickup and drop-off dates/times, pickup and drop-off locations, trip distances, itemized fares, rate types, payment types, and driver-reported passenger counts. The data used in the attached datasets were collected and provided to the NYC Taxi and Limousine Commission (TLC) by technology providers authorized under the Taxicab & Livery Passenger Enhancement Programs (TPEP/LPEP). |
Read straight from the file — download or use the API URL for the full dataset.
| 0.700 |
| valid |
| 0.700 |
| valid |
| valid |
| p[1] |
| 0.700 |
| valid |
| valid |
| valid |
| p[1] |
| 0.700 |
| valid |