Triple
T10923352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collective Rapid Deployment Forces in Central Asia |
E258001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CSTO military contingent |
C2497
|
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: CSTO military contingent Context triple: [Collective Rapid Deployment Forces in Central Asia, instanceOf, CSTO military contingent]
-
A.
Laotian military personnel
Laotian military personnel are individuals who serve in the armed forces of Laos, responsible for national defense, internal security, and supporting government operations.
-
B.
Guards field army
The Guards field army is an elite, front-line military formation composed of highly trained and well-equipped units tasked with executing critical offensive and defensive operations on behalf of a state or empire.
-
C.
Soviet field army
A Soviet field army was a large, operational-level military formation of the Soviet Armed Forces, typically comprising multiple corps or divisions, support units, and command structures, organized to conduct sustained offensive or defensive campaigns in a designated theater of operations.
-
D.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
E.
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.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.