Triple
T2358359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collective Security Treaty Organization |
E47210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental military alliance |
C280
|
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: intergovernmental military alliance Context triple: [Collective Security Treaty Organization, instanceOf, intergovernmental military alliance]
-
A.
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.
-
B.
intergovernmental organization
chosen
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
C.
multinational military forum
A multinational military forum is an organized platform where representatives from multiple countries' armed forces convene to discuss security issues, coordinate policies, share best practices, and enhance mutual understanding and cooperation.
-
D.
Economic alliance
An economic alliance is a formal or informal partnership between countries or regions designed to promote mutual economic benefits through cooperation in trade, investment, and financial policies.
-
E.
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.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:55 p.m.