Triple
T2962110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurogroup Working Group |
E80072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | euro area body |
C2118
|
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: euro area body Context triple: [Eurogroup Working Group, instanceOf, euro area body]
-
A.
economic and monetary union
An economic and monetary union is an integration arrangement in which participating countries coordinate economic policies, remove barriers to trade and capital movement, and adopt a common currency managed by a shared central monetary authority.
-
B.
European Union body
chosen
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.
-
C.
eurodistrict
A eurodistrict is a cross-border administrative and cooperation entity formed by neighboring local authorities from different European countries to coordinate services, planning, and development in a shared transnational region.
-
D.
currency union
A currency union is an agreement between two or more countries to share a common currency and monetary policy, typically managed by a joint central authority.
-
E.
outermost region of the European Union
The outermost region of the European Union is a geographically distant territory that is fully part of an EU member state and the EU itself, but benefits from specific measures to address its remoteness, insularity, and economic and social challenges.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:57 p.m.