Triple
T23078713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libby Army Airfield |
E575405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint-use military/civilian airport |
C9515
|
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: joint-use military/civilian airport Context triple: [Libby Army Airfield, instanceOf, joint-use military/civilian airport]
-
A.
civil–military airport
chosen
A civil–military airport is an aerodrome jointly used by civilian air transport services and military aviation operations, sharing infrastructure, airspace, and support facilities under coordinated management.
-
B.
privately owned airport
A privately owned airport is an airfield or aviation facility owned and operated by a non-governmental individual or entity, typically used for general aviation, corporate, or restricted-access flights rather than regular public commercial service.
-
C.
airfield
An airfield is a designated area of land equipped with runways, taxiways, and minimal support facilities for the takeoff, landing, and ground movement of aircraft.
-
D.
university-owned airport
A university-owned airport is an aviation facility operated and managed by a higher education institution, primarily supporting its academic, research, training, and transportation needs while potentially serving the surrounding community.
-
E.
domestic airport
A domestic airport is an aviation facility that handles flights operating solely within a single country's borders, providing passenger, baggage, and aircraft services for internal air travel.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:56 p.m.