Triple
T20249715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crestview as a transportation hub |
E498518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation hub role |
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: transportation hub role Context triple: [Crestview as a transportation hub, instanceOf, transportation hub role]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
transport hub identifier
A transport hub identifier uniquely labels a specific transportation node—such as an airport, train station, or bus terminal—to enable unambiguous reference and coordination across systems.
-
E.
group of passenger rail terminals
A group of passenger rail terminals is a collection of interconnected or related railway stations designed for boarding, alighting, and transferring passengers within a coordinated transport network.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:41 p.m.