Triple
T33886133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protocol No 26 on services of general interest |
E868638
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protocol to the Treaty on European Union |
C55713
|
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: Protocol to the Treaty on European Union Context triple: [Protocol No 26 on services of general interest, instanceOf, Protocol to the Treaty on European Union]
-
A.
European Union treaty protocol
chosen
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.
protocol to an international treaty
A protocol to an international treaty is a supplementary legal instrument that amends, elaborates, or adds specific obligations or procedures to an existing treaty while remaining legally linked to it.
-
C.
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.
-
D.
foundational treaty protocol
A foundational treaty protocol is a core framework of rules and procedures that governs how treaties are initiated, negotiated, formalized, and maintained between parties.
-
E.
United Nations protocol
United Nations protocol is the formal set of rules, procedures, and diplomatic customs that govern conduct, precedence, ceremonies, and official interactions within and around the United Nations.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.