Triple
T4438059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Rapid Link consortium |
E95699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport infrastructure consortium |
C4656
|
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: public transport infrastructure consortium Context triple: [Dubai Rapid Link consortium, instanceOf, public transport infrastructure consortium]
-
A.
transport infrastructure operator
A transport infrastructure operator is an entity responsible for managing, maintaining, and regulating transportation networks and facilities such as roads, railways, ports, or airports to ensure safe and efficient movement of people and goods.
-
B.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
C.
transportation network company
A transportation network company is a business that uses digital platforms, typically mobile apps, to connect passengers with drivers who provide on-demand transportation services.
-
D.
Inland Transport Committee
The Inland Transport Committee is a policy-making body that develops and coordinates international regulations, standards, and best practices to promote safe, efficient, and sustainable inland transport systems.
-
E.
transportation organization
chosen
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:31 p.m.