Triple
T36914794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyce Airport |
E913014
|
entity |
| Predicate | formerMilitaryUser |
P192670
|
FINISHED |
| Object | Royal Air Force |
—
|
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: Royal Air Force | Statement: [Dyce Airport, formerMilitaryUser, Royal Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerMilitaryUser Context triple: [Dyce Airport, formerMilitaryUser, Royal Air Force]
-
A.
retiredFromUSMilitary
Indicates that an individual previously served in the United States military and has formally ended their military career or service.
-
B.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
C.
usedByBranchOfMilitary
chosen
Indicates that something is utilized or operated by a specific branch of a country's military forces.
-
D.
hadMilitaryPost
Indicates that an entity held an official position or assignment within a military organization.
-
E.
hadMilitaryServiceFrom
Indicates that an entity performed or was engaged in military service starting from a specified point in time.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:13 p.m.