Triple
T2489443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission d’Organisation des Régions Fortifiées |
E52004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military planning commission |
C298
|
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 commission Context triple: [Commission d’Organisation des Régions Fortifiées, instanceOf, military planning commission]
-
A.
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.
-
B.
military organization
chosen
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.
-
C.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
-
D.
military project
A military project is a coordinated, goal-driven initiative undertaken by armed forces or defense organizations to develop, test, or deploy capabilities, technologies, or operations that enhance national security and military effectiveness.
-
E.
military mission
A military mission is a coordinated operation undertaken by armed forces to achieve specific strategic, operational, or tactical objectives within defined constraints and rules of engagement.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:45 p.m.