Triple
T24787072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Officer Commanding-in-Chief Middle East Command (RAF) |
E620146
|
entity |
| Predicate | isHeldByRank |
P148088
|
FINISHED |
| Object | Air Chief Marshal |
—
|
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: Air Chief Marshal | Statement: [Air Officer Commanding-in-Chief Middle East Command (RAF), isHeldByRank, Air Chief Marshal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeldByRank Context triple: [Air Officer Commanding-in-Chief Middle East Command (RAF), isHeldByRank, Air Chief Marshal]
-
A.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control of another entity.
-
B.
memberHeldRank
chosen
Indicates that a member possessed or occupied a specific rank or position within an organization or hierarchy.
-
C.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
D.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
E.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110071008190a430ca780b567fe4 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:46 a.m.