Triple
T36460342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold Bay Airport |
E898271
|
entity |
| Predicate | isFormerMilitaryAirfield |
P90511
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Cold Bay Airport, isFormerMilitaryAirfield, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerMilitaryAirfield Context triple: [Cold Bay Airport, isFormerMilitaryAirfield, true]
-
A.
hasFormerMilitaryAirfield
chosen
Indicates that an entity possesses or is associated with an airfield that was previously used for military purposes but is no longer active as such.
-
B.
openedAsMilitaryAirfield
Indicates that an airfield was originally established and began operation specifically for military aviation use.
-
C.
formerAerodrome
Indicates that a location was previously used as an aerodrome (airfield) but no longer serves that function.
-
D.
airfieldDecommissioned
Indicates that an airfield has been officially taken out of service and is no longer used for regular aviation operations.
-
E.
airfieldUsedDuring
Indicates that an airfield was in operational use during a specified time period or event.
- 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_69f76e57f08481908593bd0bc34581c8 |
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.