Triple
T20899055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse E checkpoint |
E514619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport infrastructure facility |
C10698
|
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: transport infrastructure facility Context triple: [Concourse E checkpoint, instanceOf, transport infrastructure facility]
-
A.
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.
-
B.
transport infrastructure name
A transport infrastructure name identifies a specific facility or network element used for the movement of people or goods, such as a road, railway line, airport, or port.
-
C.
infrastructure facility
chosen
An infrastructure facility is a physical installation or complex that provides essential services or support functions—such as transportation, utilities, communication, or public safety—necessary for the operation and development of a community or region.
-
D.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
E.
ground transportation facility
A ground transportation facility is a designated location that supports the movement, transfer, and management of passengers or goods via land-based modes such as buses, trains, cars, or trucks.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:47 p.m.