Triple
T33093828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Sergeant Major (USA) |
E846854
|
entity |
| Predicate | NATO rank code |
P6062
|
FINISHED |
| Object | OR-9 |
—
|
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: OR-9 | Statement: [Command Sergeant Major (USA), NATO rank code, OR-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATO rank code Context triple: [Command Sergeant Major (USA), NATO rank code, OR-9]
-
A.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
B.
roleInNATO
Indicates the specific capacity, position, or function an entity holds within the organizational or operational structure of NATO.
-
C.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
D.
militaryRankGroup
Indicates that one entity belongs to, or is categorized within, a particular group or classification of military ranks.
-
E.
militaryRankScope
Indicates the hierarchical level or range of authority that a military rank applies to within an organizational or operational 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.