Triple
T5085879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Rapid Reaction Corps |
E114636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NATO formation |
C11966
|
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: NATO formation Context triple: [Allied Rapid Reaction Corps, instanceOf, NATO formation]
-
A.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
-
B.
Cold War organization
A Cold War organization is an entity—such as a military alliance, intelligence agency, or political bloc—formed or structured primarily to advance strategic, ideological, or security objectives during the geopolitical rivalry between the United States and the Soviet Union from roughly 1947 to 1991.
-
C.
NATO administrative division
chosen
A NATO administrative division is an organizational unit within the North Atlantic Treaty Organization responsible for managing specific functions, regions, or operational domains to support the alliance’s political, military, and logistical activities.
-
D.
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.
-
E.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:40 p.m.