Triple
T33093832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Sergeant Major (USA) |
E846854
|
entity |
| Predicate | higher rank |
P88112
|
FINISHED |
| Object | Sergeant Major of the Army |
—
|
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: Sergeant Major of the Army | Statement: [Command Sergeant Major (USA), higher rank, Sergeant Major of the Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higher rank Context triple: [Command Sergeant Major (USA), higher rank, Sergeant Major of the Army]
-
A.
higherRankHas
chosen
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
B.
higherRankDescription
Indicates that one entity holds a superior or more senior rank or status compared to another entity.
-
C.
highestRanking
Indicates that one entity holds the top or most senior rank relative to a set of other entities.
-
D.
nextHigherRank
Indicates that one entity holds the immediately superior rank or level in a hierarchy relative to another entity.
-
E.
isHighRanking
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:26 a.m.