Triple
T34800347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FlixCar |
E1003202
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | carpooling service brand |
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: carpooling service brand Context triple: [FlixCar, instanceOf, carpooling service brand]
-
A.
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.
-
B.
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.
-
C.
transport brand
A transport brand is a conceptual class representing a company or entity that provides transportation services or products, characterized by attributes like name, logo, service types, and reputation, and behaviors such as marketing, service delivery, and customer support.
-
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 services company
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.