Triple
T13984772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of Canonical Communion |
E336409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reunification agreement |
C24423
|
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: reunification agreement Context triple: [Act of Canonical Communion, instanceOf, reunification agreement]
-
A.
unification act
chosen
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.
-
B.
union republic
A union republic is a constituent political unit within a federal or quasi-federal state, typically possessing its own government and constitution while remaining subordinate to the overarching union authority.
-
C.
continental union
A continental union is a political and economic organization formed by multiple countries within the same continent to coordinate policies, promote integration, and pursue shared goals.
-
D.
Rechtsgrundlage der deutschen Wiedervereinigung
Die Rechtsgrundlage der deutschen Wiedervereinigung umfasst das Zusammenspiel von innerstaatlichen und völkerrechtlichen Normen – insbesondere den Einigungsvertrag, das Grundgesetz (insb. Art. 23 a.F. und Art. 146 GG) sowie den Zwei-plus-Vier-Vertrag – die gemeinsam die staatliche Einheit Deutschlands rechtlich ermöglichten und absicherten.
-
E.
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.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:18 p.m.