Triple
T31895928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber driver-partners |
E814282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ride-hailing drivers |
C46132
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ride-hailing drivers Context triple: [Uber driver-partners, instanceOf, ride-hailing drivers]
-
A.
taxi driver
A taxi driver is a professional who transports passengers to their destinations in a licensed vehicle, following traffic laws and using knowledge of local routes to provide safe and efficient travel.
-
B.
robotaxi operator
A robotaxi operator is an entity that manages, monitors, and maintains a fleet of autonomous taxis, ensuring safe, reliable, and compliant driverless transportation services for passengers.
-
C.
mobility services provider
chosen
A mobility services provider is an organization that offers and manages transportation solutions—such as ride-hailing, car-sharing, bike or scooter rentals, and integrated transit services—to enable people and goods to move efficiently from one place to another.
-
D.
transport technology company
A transport technology company develops and provides innovative digital solutions, platforms, and systems that optimize the planning, operation, and management of transportation services and infrastructure.
-
E.
transportation service
A transportation service is a system or business that moves people or goods from one location to another using various modes of transport under defined schedules, routes, and conditions.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:58 p.m.