Triple
T32179261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Master Sergeant |
E821937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States military rank |
C26263
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: United States military rank Context triple: [Senior Master Sergeant, instanceOf, United States military rank]
-
A.
United States Marine Corps rank
A United States Marine Corps rank represents a specific level of authority, responsibility, and seniority within the Marine Corps’ structured hierarchy, defining a Marine’s role, duties, and position in the chain of command.
-
B.
military rank and position
A military rank and position represents an individual's formal level of authority and designated role within an armed forces hierarchy, defining their responsibilities, command scope, and relationship to other personnel.
-
C.
U.S. Navy enlisted rank
chosen
A U.S. Navy enlisted rank is a hierarchical position held by non-officer sailors that defines their level of authority, responsibility, and pay grade within the Navy’s enlisted structure.
-
D.
military-equivalent rank
A military-equivalent rank is a formal position or title in a non-military organization that is defined to correspond in status, authority, or protocol to a specific rank within a military hierarchy.
-
E.
Soviet military rank position
A Soviet military rank position represents a specific hierarchical status and role within the armed forces of the former Soviet Union, defining an individual's authority, responsibilities, and command relationships.
- F. None of above.
Provenance (1 batch)
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:34 a.m.