Triple
T33351223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlatelolco–La Raza–Deportivo 18 de Marzo section |
E853945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport infrastructure segment |
C61166
|
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 segment Context triple: [Tlatelolco–La Raza–Deportivo 18 de Marzo section, instanceOf, transport infrastructure segment]
-
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 sector
The transport sector encompasses all systems, services, and infrastructure involved in moving people and goods by road, rail, air, and water.
-
C.
rail transportation infrastructure
Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
-
D.
transport corridor segment
chosen
A transport corridor segment is a defined linear portion of a transportation route (such as a road, rail line, or shipping lane) characterized by consistent physical, operational, and regulatory attributes used for planning, management, and analysis.
-
E.
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.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.