Triple
T8281747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CoR |
E193689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European Committee of the Regions |
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: European Committee of the Regions Context triple: [CoR, instanceOf, European Committee of the Regions]
-
A.
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.
-
B.
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.
-
C.
European party federation
A European party federation is a transnational political organization that unites national political parties from multiple European countries around shared ideological goals and coordinates their activities at the European level.
-
D.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
-
E.
organ of the Council of Europe
An organ of the Council of Europe is an institutional body established by the Council’s Statute or subsequent agreements, endowed with specific functions and powers to contribute to the organization’s objectives in democracy, human rights, and the rule of law.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:51 p.m.