Triple
T20075449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mineta San José International Airport (flight path area) |
E499850
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | approach and departure corridor |
C2952
|
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: approach and departure corridor Context triple: [Mineta San José International Airport (flight path area), instanceOf, approach and departure corridor]
-
A.
highway approach route
A highway approach route is a roadway segment or path that guides vehicles from local or arterial roads onto a highway, facilitating safe and efficient merging into higher-speed traffic.
-
B.
airport runway
An airport runway is a long, specially prepared strip of land or pavement where aircraft take off and land, designed with specific markings, lighting, and surface strength to ensure safe operations.
-
C.
roadway approach
A roadway approach is the segment of a road leading up to an intersection, junction, or control device, where vehicles transition from through movement to potential stopping, turning, or yielding maneuvers.
-
D.
transport corridor
chosen
A transport corridor is a designated route or geographic band that concentrates and connects major transportation infrastructure—such as roads, railways, ports, and logistics hubs—to facilitate efficient movement of people and goods between key locations.
-
E.
passenger terminal concourse
A passenger terminal concourse is a large, central circulation space within a transport terminal where travelers move between entrances, ticketing, security, and boarding areas, often containing seating, retail, and information 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:40 p.m.