Triple
T8849976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty establishing a Single Council and a Single Commission of the European Communities |
E210613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Merger Treaty |
C88
|
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: Merger Treaty Context triple: [Treaty establishing a Single Council and a Single Commission of the European Communities, instanceOf, Merger Treaty]
-
A.
treaty
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
founding treaty
chosen
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.
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.
-
D.
unification act
A unification act is a formal legal or political measure that merges separate entities—such as states, organizations, or systems—into a single, integrated whole under a common authority or framework.
-
E.
treaty annex
A treaty annex is a supplementary document attached to a main treaty that provides detailed provisions, technical specifications, or additional terms that form an integral part of the overall agreement.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:49 p.m.