Triple
T32118657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnery Sergeant (USMC) |
E820305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior non-commissioned officer rank |
C3908
|
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: senior non-commissioned officer rank Context triple: [Gunnery Sergeant (USMC), instanceOf, senior non-commissioned officer rank]
-
A.
senior enlisted rank
chosen
A senior enlisted rank is a high-level non-commissioned position in the military hierarchy, typically responsible for expert technical skills, leadership, and advising officers on enlisted matters.
-
B.
noncommissioned officer rank
A noncommissioned officer rank is a level of military authority held by enlisted personnel who have been given leadership and supervisory responsibilities without being commissioned as officers.
-
C.
noncommissioned officer rank
A noncommissioned officer rank is a level of military authority held by enlisted personnel who have been promoted to leadership positions without receiving a formal officer commission.
-
D.
senior commissioned officer rank
A senior commissioned officer rank is a high-level military leadership position held by experienced officers who command large units, shape strategic decisions, and hold significant authority and responsibility within the armed forces hierarchy.
-
E.
field-grade officer rank
A field-grade officer rank is a mid-level commissioned officer position, typically including majors, lieutenant colonels, and colonels, responsible for commanding battalion- to brigade-sized units and performing higher-level staff duties.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:28 a.m.