Triple
T1363358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 13B Cannon Crewmember |
E29146
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | enlisted military occupational specialty |
C6987
|
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: enlisted military occupational specialty Context triple: [13B Cannon Crewmember, instanceOf, enlisted military occupational specialty]
-
A.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
B.
military office
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support military operations.
-
C.
military-adjacent uniformed service
A military-adjacent uniformed service is an organized, government-sanctioned body whose members wear standardized uniforms and perform defense-, security-, or support-related functions alongside or in coordination with the armed forces, but are not formally part of the military.
-
D.
senior enlisted rank
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.
-
E.
military appointment
A military appointment is an official position or duty assigned to a service member within the armed forces, defining their role, responsibilities, and authority.
- F. None of above. chosen
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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:57 p.m.