Triple
T8050591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Committee under the Withdrawal Agreement |
E187662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK–EU governance body |
C14427
|
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: UK–EU governance body Context triple: [Joint Committee under the Withdrawal Agreement, instanceOf, UK–EU governance body]
-
A.
European Union body
A European Union body is an institution, agency, or other organizational entity established by the EU’s founding treaties or secondary legislation to perform specific political, regulatory, advisory, or administrative functions within the Union’s governance framework.
-
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.
European intergovernmental organization
A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
-
D.
European organisation
chosen
A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
-
E.
government agency of the United Kingdom
A government agency of the United Kingdom is an official public body established by the UK government to carry out specific administrative, regulatory, or service-delivery functions on its behalf.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:24 p.m.