Triple
T810640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belfast International Airport |
E17535
|
entity |
| Predicate | usedAsMilitaryAirfield |
P9620
|
FINISHED |
| Object | Royal Air Force base |
—
|
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: Royal Air Force base | Statement: [Belfast International Airport, usedAsMilitaryAirfield, Royal Air Force base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMilitaryAirfield Context triple: [Belfast International Airport, usedAsMilitaryAirfield, Royal Air Force base]
-
A.
openedAsMilitaryAirfield
Indicates that an airfield was originally established and began operation specifically for military aviation use.
-
B.
containsAirfield
Indicates that a location or area includes at least one airfield within its boundaries.
-
C.
hasRunwayUse
Indicates that a particular runway is authorized or designated for use by a specific aircraft, operation, or purpose.
-
D.
usedInAviationAs
chosen
Indicates that something serves a particular role, function, or application within the field of aviation.
-
E.
usedInAviation
Indicates that something is employed or applied within the field or context of aviation.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab4c7418819085cb64c6bf5fa70c |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa73df08819096d0553a4b2509de |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.