Triple
T33512265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protocol No 30 on the application of the Charter to Poland and the United Kingdom |
E858280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | annex to the EU Treaties |
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: annex to the EU Treaties Context triple: [Protocol No 30 on the application of the Charter to Poland and the United Kingdom, instanceOf, annex to the EU Treaties]
-
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.
annex to international agreement
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
-
C.
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.
-
D.
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.
-
E.
annex
An annex is a supplementary building or section that is attached to or associated with a main structure to provide additional space or functions.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.