Triple
T22115546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty on the Creation of a Community of Russia and Belarus |
E546531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | founding document of the Union State |
C531
|
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: founding document of the Union State Context triple: [Treaty on the Creation of a Community of Russia and Belarus, instanceOf, founding document of the Union State]
-
A.
founding document
chosen
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
B.
founding treaty
A founding treaty is a formal, binding international agreement that establishes, constitutes, and defines the core structures, powers, and purposes of an international organization or political union.
-
C.
confederation of states
A confederation of states is a union of sovereign states that voluntarily cooperate on certain common matters through a central body that has limited authority and depends on the member states for implementation and enforcement.
-
D.
founding document of the Arab League
The founding document of the Arab League is the formal treaty that established the organization’s principles, structure, and objectives for cooperation among its member Arab states.
-
E.
foundational document of Mercosur
A foundational document of Mercosur is a formal legal instrument, such as a treaty or protocol, that establishes, structures, or significantly governs the creation, principles, institutions, and functioning of the Southern Common Market (Mercosur).
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.