Triple
T27979303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialised Committee on financial provisions |
E706574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU–UK joint body |
C23467
|
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: EU–UK joint body Context triple: [Specialised Committee on financial provisions, instanceOf, EU–UK joint body]
-
A.
UK–EU body
chosen
A UK–EU body is a joint institutional entity established by agreements between the United Kingdom and the European Union to oversee, implement, or manage specific aspects of their bilateral relationship.
-
B.
EU–US body
A formal, institutionalized entity that facilitates structured political, economic, and regulatory dialogue and cooperation between the European Union and the United States.
-
C.
Joint committee of the Parliament of the United Kingdom
A Joint Committee of the Parliament of the United Kingdom is a committee composed of members from both the House of Commons and the House of Lords that examines specific issues, legislation, or matters of public importance.
-
D.
U.S.–Canada joint body
A U.S.–Canada joint body is a binational institution established by the United States and Canada to coordinate, manage, or regulate shared interests such as natural resources, trade, security, or environmental protection across their common border.
-
E.
joint British–Irish institution
A joint British–Irish institution is an organization or body formally established and operated by both the United Kingdom and Ireland to manage shared interests, cooperation, or governance across their mutual areas of concern.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:43 p.m.