Triple
T33879437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRACON |
E868444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | terminal radar approach control |
C3808
|
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: terminal radar approach control Context triple: [TRACON, instanceOf, terminal radar approach control]
-
A.
air traffic control tower
A structure at an airport from which air traffic controllers monitor and direct aircraft movements on the ground and in the airspace around the airport to ensure safe and efficient operations.
-
B.
radar intercept officer
A radar intercept officer is a specialized flight crew member responsible for operating and interpreting an aircraft’s radar and sensor systems to detect, track, and engage targets while assisting with navigation and tactical decision-making.
-
C.
private aviation terminal
A private aviation terminal is a specialized airport facility that provides exclusive, streamlined services and amenities for private and corporate aircraft, their passengers, and crews.
-
D.
air navigation organization
chosen
An air navigation organization is an entity responsible for planning, managing, and controlling the safe and efficient movement of aircraft through designated airspace using air traffic services, communication, navigation, and surveillance systems.
-
E.
VORTAC station
A VORTAC station is a ground-based aviation navigational facility that combines VOR (VHF Omnidirectional Range) and TACAN (Tactical Air Navigation) systems to provide both azimuth and distance information to aircraft.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.