Triple
T4812685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Junction Regional Airport |
E107108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial service airport |
C16416
|
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: commercial service airport Context triple: [Grand Junction Regional Airport, instanceOf, commercial service airport]
-
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.
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.
-
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 business travelers.
-
E.
commercial airline
A commercial airline is a company that provides scheduled air transportation services for passengers and cargo using a fleet of aircraft.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:23 p.m.