Triple
T36479247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stapleton Airfield |
E898762
|
entity |
| Predicate | wasMajorAirportFor |
P75084
|
FINISHED |
| Object | Rocky Mountain region |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Rocky Mountain region | Statement: [Stapleton Airfield, wasMajorAirportFor, Rocky Mountain region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorAirportFor Context triple: [Stapleton Airfield, wasMajorAirportFor, Rocky Mountain region]
-
A.
isMajorRegionalAirportFor
chosen
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
B.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
C.
replacedAsMainAirportFor
Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
-
D.
isMajorCargoAirport
Indicates that an airport primarily handles large volumes of cargo traffic and serves as a significant freight hub.
-
E.
hasPrimaryAirportRole
Indicates that an entity holds the main or principal functional role associated with an airport.
- F. None of above.
Provenance (3 batches)
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.