Triple
T12925002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Warrant Officer 2 |
E309220
|
entity |
| Predicate | positionInCorps |
P342
|
FINISHED |
| Object | above Warrant Officer 1 |
—
|
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: above Warrant Officer 1 | Statement: [Chief Warrant Officer 2, positionInCorps, above Warrant Officer 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCorps Context triple: [Chief Warrant Officer 2, positionInCorps, above Warrant Officer 1]
-
A.
militaryRank
chosen
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
B.
officerCorps
Indicates that an entity belongs to, is part of, or is associated with a group or body of officers within an organization or institution.
-
C.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
D.
positionInBattle
Indicates the specific role or placement an entity occupies within the formation or structure of a battle.
-
E.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e9576c81908eb59569af6da877 |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.