Triple
T37767718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 Accession Treaty |
E941460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty of the European Communities |
C566
|
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: treaty of the European Communities Context triple: [1981 Accession Treaty, instanceOf, treaty of the European Communities]
-
A.
European Union treaty protocol
A European Union treaty protocol is a formal, legally binding addendum or supplement to an EU founding or amending treaty that clarifies, extends, or specifies particular provisions, obligations, or arrangements among member states.
-
B.
European Union convention
A European Union convention is a formal international agreement between EU member states, or between the EU and other parties, that establishes common rules, standards, or cooperation frameworks in specific policy areas.
-
C.
treaty
chosen
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.
-
D.
Hague Convention
The Hague Convention is a series of international treaties and declarations developed at The Hague that establish rules and standards for various aspects of international law, including the conduct of war, protection of children, and civil procedure.
-
E.
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.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.