Triple
T13044458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provost Marshal (Army) |
E327281
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military police leadership role |
C449
|
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: military police leadership role Context triple: [Provost Marshal (Army), instanceOf, military police leadership role]
-
A.
military leadership framework
A military leadership framework is a structured model that defines the principles, competencies, behaviors, and decision-making processes required to effectively lead individuals and units in military operations and organizational contexts.
-
B.
political-military role
A political-military role is a position that combines formal authority and responsibilities in both governmental decision-making and the planning, direction, or oversight of military or security forces.
-
C.
military education leadership position
A military education leadership position is a role responsible for directing, managing, and improving the training, professional development, and academic programs that prepare military personnel for effective service and leadership.
-
D.
military officer
chosen
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.
-
E.
paramilitary rank
A paramilitary rank is a hierarchical title or position within an organized, non-military armed group that mirrors military ranking structures to define authority, responsibility, and command.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:56 p.m.