Triple
T16515621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shura-e Nazar |
E401175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military-political alliance |
C22718
|
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-political alliance Context triple: [Shura-e Nazar, instanceOf, military-political alliance]
-
A.
political-military alliance
chosen
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
B.
historical alliance
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
C.
multinational military coalition
A multinational military coalition is a temporary or long-term alliance of armed forces from multiple sovereign states that coordinate resources, strategy, and operations to achieve shared security or defense objectives.
-
D.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
E.
religious and political alliance
A religious and political alliance is a coalition in which faith-based groups and political actors formally or informally coordinate their agendas, resources, and influence to pursue shared ideological, social, or policy goals.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:14 a.m.