Triple
T2996208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Air Force personnel |
E81072
|
entity |
| Predicate | typicalRankStructure |
P2727
|
FINISHED |
| Object | commissioned officers |
—
|
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: commissioned officers | Statement: [Royal Air Force personnel, typicalRankStructure, commissioned officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRankStructure Context triple: [Royal Air Force personnel, typicalRankStructure, commissioned officers]
-
A.
typicalRank
Indicates the usual or most common rank or position an entity holds within a given ordering or hierarchy.
-
B.
typicalRankRange
Indicates the usual or most common range of ranks or ordered positions that an entity typically occupies within a ranking or hierarchy.
-
C.
usesRankStructure
chosen
Indicates that an entity organizes its members or components according to a defined hierarchical rank structure.
-
D.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f481688190ae8cd1e057f9dfc7 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.