Triple
T23151464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Elmhirst |
E578333
|
entity |
| Predicate | positionHeld |
P8
|
FINISHED |
| Object | Air Officer Commanding, No. 23 (Training) Group |
—
|
NE NERFINISHED |
How this triple was built (3 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: Air Officer Commanding, No. 23 (Training) Group | Statement: [Thomas Elmhirst, positionHeld, Air Officer Commanding, No. 23 (Training) Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Air Officer Commanding, No. 23 (Training) Group Context triple: [Thomas Elmhirst, positionHeld, Air Officer Commanding, No. 23 (Training) Group]
-
A.
Air Officer Commanding, No. 21 (Training) Group
Air Officer Commanding, No. 21 (Training) Group was a senior Royal Air Force command role responsible for overseeing a major training group within the RAF.
-
B.
Air Officer Commanding No. 22 Group
The Air Officer Commanding No. 22 Group is the senior Royal Air Force officer responsible for overseeing the service’s training and education establishments and related operational support functions.
-
C.
Air Officer Commanding No. 38 Group
The Air Officer Commanding No. 38 Group is the senior Royal Air Force officer responsible for leading and overseeing the operations, personnel, and resources of No. 38 Group.
-
D.
Air Officer Commanding No. 83 Group
Air Officer Commanding No. 83 Group was a senior Royal Air Force command role responsible for leading and overseeing the operations of No. 83 Group.
-
E.
Air Officer Commanding No. 232 Group RAF
Air Officer Commanding No. 232 Group RAF was a senior Royal Air Force command appointment responsible for overseeing the operations and administration of No. 232 Group.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Air Officer Commanding, No. 23 (Training) Group Target entity description: Air Officer Commanding, No. 23 (Training) Group was a senior Royal Air Force command role responsible for overseeing a major training group within the service.
-
A.
Air Officer Commanding, No. 21 (Training) Group
Air Officer Commanding, No. 21 (Training) Group was a senior Royal Air Force command role responsible for overseeing a major training group within the RAF.
-
B.
Air Officer Commanding No. 22 Group
The Air Officer Commanding No. 22 Group is the senior Royal Air Force officer responsible for overseeing the service’s training and education establishments and related operational support functions.
-
C.
Air Officer Commanding No. 38 Group
The Air Officer Commanding No. 38 Group is the senior Royal Air Force officer responsible for leading and overseeing the operations, personnel, and resources of No. 38 Group.
-
D.
Air Officer Commanding No. 83 Group
Air Officer Commanding No. 83 Group was a senior Royal Air Force command role responsible for leading and overseeing the operations of No. 83 Group.
-
E.
Air Officer Commanding No. 232 Group RAF
Air Officer Commanding No. 232 Group RAF was a senior Royal Air Force command appointment responsible for overseeing the operations and administration of No. 232 Group.
- F. None of above. chosen
Provenance (2 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ef982488190984a6358bdcd577c |
completed | April 29, 2026, 4:54 a.m. |
Created at: April 17, 2026, 4:01 p.m.