Triple
T33093830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Sergeant Major (USA) |
E846854
|
entity |
| Predicate | rank group |
P173591
|
FINISHED |
| Object | Noncommissioned officer |
—
|
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: Noncommissioned officer | Statement: [Command Sergeant Major (USA), rank group, Noncommissioned officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rank group Context triple: [Command Sergeant Major (USA), rank group, Noncommissioned officer]
-
A.
rankGroupOf
chosen
Indicates a relationship where entities are grouped together and assigned a shared rank or ordered position within a larger ranking system.
-
B.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
C.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
D.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
E.
rankIn
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
- 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_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.