Triple
T9631092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Lossiemouth |
E232803
|
entity |
| Predicate | revertedToRAFControl |
P3912
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [RAF Lossiemouth, revertedToRAFControl, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revertedToRAFControl Context triple: [RAF Lossiemouth, revertedToRAFControl, 1972]
-
A.
transferredControlFrom
Indicates that authority or control over something has been moved or handed over from one entity to another.
-
B.
reconvertedTo
Indicates that something has been changed back or restored to a previous state, form, or condition it once had.
-
C.
retrocededTo
chosen
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
formerControlBy
Indicates that one entity previously exercised control or authority over another entity, but no longer does so.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2621408190bfe2ea5a05359ee0 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.