Triple
T9139853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrobús Line 3 stations |
E219295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport infrastructure element collection |
C2489
|
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 element collection Context triple: [Metrobús Line 3 stations, instanceOf, public transport infrastructure element collection]
-
A.
public transportation infrastructure
chosen
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.
-
B.
transportation corridors collection
A transportation corridors collection is an organized set of linear pathways—such as roads, railways, and transit routes—grouped for managing, analyzing, or planning movement across a region.
-
C.
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.
-
D.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
E.
road transport node
A road transport node is a specific location within a road network where vehicles and travelers converge, diverge, or transfer, such as intersections, terminals, or hubs.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:19 p.m.