Triple
T36189467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | served by Sachs Harbour Airport |
E1046945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport service relation |
C65044
|
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: airport service relation Context triple: [served by Sachs Harbour Airport, instanceOf, airport service relation]
-
A.
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.
-
B.
airport service area
An airport service area is the designated zone within and around an airport where operational, maintenance, and support activities are conducted to facilitate aircraft handling and passenger services.
-
C.
airport service program
An airport service program is a coordinated set of services and processes designed to manage and enhance passenger, baggage, and aircraft handling throughout all stages of airport operations.
-
D.
air service
Air service is the provision of transportation and related support operations using aircraft to move passengers, cargo, or mail between locations.
-
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. chosen
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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.