Triple
T2146411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownsville–Matamoros crossing |
E47075
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport infrastructure complex |
C82
|
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 complex Context triple: [Brownsville–Matamoros crossing, instanceOf, transport infrastructure complex]
-
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.
combined civic building and transportation hub
A combined civic building and transportation hub is a multifunctional public facility that integrates government or community services with major transit infrastructure to centralize access, improve connectivity, and enhance urban efficiency.
-
C.
transport hub
chosen
A transport hub is a central location where multiple modes or routes of transportation intersect, enabling the efficient transfer of passengers or goods between them.
-
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.
railway engineering complex
A railway engineering complex is an integrated facility where railway infrastructure, rolling stock, and related systems are designed, constructed, tested, maintained, and managed.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:44 p.m.