Triple
T17246365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Heyford |
E418635
|
entity |
| Predicate | RAFBaseColdWarRole |
P126548
|
FINISHED |
| Object | US strategic bomber 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: US strategic bomber base | Statement: [Upper Heyford, RAFBaseColdWarRole, US strategic bomber base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RAFBaseColdWarRole Context triple: [Upper Heyford, RAFBaseColdWarRole, US strategic bomber base]
-
A.
RAFRole
Indicates that an entity holds or is assigned a specific role within the Royal Air Force.
-
B.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
-
C.
roleDuringBlackHawkWar
Indicates the specific role, position, or function an entity held during the Black Hawk War.
-
D.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:39 a.m.