Triple
T5799914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Current Military Operations Service |
E128594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military planning unit |
C8231
|
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 planning unit Context triple: [Current Military Operations Service, instanceOf, military planning unit]
-
A.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
operational unit
chosen
An operational unit is an organized group, department, or component within a larger system that performs specific tasks or functions to achieve defined operational objectives.
-
C.
military planning document
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
D.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
E.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.