Triple
T15539977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Kinloss |
E370448
|
entity |
| Predicate | roleAfterRAFClosure |
P119100
|
FINISHED |
| Object | British Army barracks |
—
|
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: British Army barracks | Statement: [RAF Kinloss, roleAfterRAFClosure, British Army barracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAfterRAFClosure Context triple: [RAF Kinloss, roleAfterRAFClosure, British Army barracks]
-
A.
roleAfterManaging
Indicates the role or position an entity assumes after it has finished managing another entity or activity.
-
B.
roleAfterConversion
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
-
C.
roleAfterRefounding
Indicates the role or position an entity holds following the refounding or re-establishment of an organization, institution, or similar entity.
-
D.
roleAfterDeathFilledBy
Indicates that a role or position previously held by someone who has died is subsequently occupied or taken over by another entity.
-
E.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
- F. None of above. chosen
Provenance (4 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:07 a.m.