Triple
T5800740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Affairs Standing Capacity |
E128614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rapidly deployable capacity |
C18888
|
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: rapidly deployable capacity Context triple: [Civil Affairs Standing Capacity, instanceOf, rapidly deployable capacity]
-
A.
NATO capability
A NATO capability is a specific military, political, or logistical asset, function, or competence that member states collectively develop, maintain, and coordinate to fulfill the Alliance’s strategic objectives and operational requirements.
-
B.
military capability area
A military capability area is a distinct domain of military functions, resources, and competencies grouped together to achieve specific defense and operational objectives.
-
C.
intelligence, surveillance and reconnaissance capability
Intelligence, surveillance and reconnaissance capability is the integrated ability to collect, process, analyze and disseminate information from multiple sources to provide timely situational awareness and support informed decision-making.
-
D.
NATO rapid reaction corps headquarters
The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
-
E.
military mobilization
Military mobilization is the organized process by which a state prepares and deploys its armed forces and resources for war or national defense.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.