Triple
T935972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Air Route Traffic Control Center |
E20194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Air Route Traffic Control Center |
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: Air Route Traffic Control Center Context triple: [Washington Air Route Traffic Control Center, instanceOf, Air Route Traffic Control Center]
-
A.
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.
-
B.
airport system
An airport system is an integrated network of facilities, services, and processes that manages the safe, efficient movement of passengers, cargo, and aircraft within and around an airport.
-
C.
public airport
A public airport is a government- or publicly-owned aviation facility open for use by the general public, providing infrastructure and services for commercial, private, and cargo air transportation.
-
D.
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.
-
E.
airport authority
An airport authority is an organization responsible for the ownership, management, operation, and regulation of an airport or group of airports, ensuring safe, efficient, and compliant aviation services and facilities.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.