Triple
T10644650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern and Midland Regional Assembly area |
E250806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NUTS2 region |
C28788
|
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: NUTS2 region Context triple: [Eastern and Midland Regional Assembly area, instanceOf, NUTS2 region]
-
A.
NUTS 3 region
A NUTS 3 region is a small-scale territorial unit within the European Union’s Nomenclature of Territorial Units for Statistics, typically representing counties, districts, or equivalent local administrative areas used for regional statistics and policy.
-
B.
NUTS-1 region
A NUTS-1 region is a large, first-level territorial unit used by the European Union for statistical, economic, and regional policy analysis.
-
C.
NUTS 2 statistical region of France
A NUTS 2 statistical region of France is a mid-level territorial unit defined by the EU’s Nomenclature of Territorial Units for Statistics, used for regional statistics, analysis, and policy implementation within the country.
-
D.
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.
-
E.
NUTS 2 region of Greece
A NUTS 2 region of Greece is a territorial statistical unit defined by the EU’s Nomenclature of Territorial Units for Statistics at level 2, used for regional analysis, policy implementation, and allocation of structural funds within Greece.
- F. None of above. chosen
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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:05 p.m.