Triple
T28070978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machrihanish |
E709398
|
entity |
| Predicate | formerAirbaseName |
P170281
|
FINISHED |
| Object | RAF Machrihanish |
—
|
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: RAF Machrihanish | Statement: [Machrihanish, formerAirbaseName, RAF Machrihanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAirbaseName Context triple: [Machrihanish, formerAirbaseName, RAF Machrihanish]
-
A.
formerAerodrome
Indicates that a location was previously used as an aerodrome (airfield) but no longer serves that function.
-
B.
hasFormerMilitaryAirfield
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.
-
C.
airfieldAlsoKnownAs
chosen
Indicates that an airfield is referred to by an alternative name or alias.
-
D.
formerMilitaryBase
Indicates that a location was previously used as a military base but no longer serves that function.
-
E.
isPrincipalAirBaseOf
Indicates that one location serves as the main or primary air base for a specified military unit, organization, or region.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 27, 2026, 8:46 p.m.