Triple
T4920410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Traffic Organization |
E110450
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air navigation service provider |
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 navigation service provider Context triple: [Air Traffic Organization, instanceOf, air navigation service provider]
-
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.
air transport service provider
An air transport service provider is an organization that offers the commercial operation, management, and coordination of aircraft and related services to move passengers or cargo between locations.
-
C.
airport services provider
An airport services provider is an organization that delivers ground handling, passenger assistance, cargo management, and related operational support services to airlines and airport authorities.
-
D.
business aviation airport
A business aviation airport is a specialized airfield designed primarily to serve private, corporate, and charter aircraft with tailored facilities and services for non-scheduled, business-focused air travel.
-
E.
business aviation airport
A business aviation airport is a specialized airfield designed primarily to serve private, corporate, and charter aircraft with tailored facilities and services for business travelers.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:29 p.m.