Triple
T3958492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UKC |
E85839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NUTS 1 region code |
C13738
|
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: NUTS 1 region code Context triple: [UKC, instanceOf, NUTS 1 region code]
-
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
chosen
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.
ISO 3166-2 entry
An ISO 3166-2 entry represents a standardized code and associated metadata that uniquely identifies a principal subdivision (such as a state, province, or region) within a specific country defined in ISO 3166-1.
-
E.
ISO 3166-1 numeric country code
A three-digit numeric code defined by the ISO 3166-1 standard that uniquely identifies each recognized country or territory for use in international data exchange and classification.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:31 p.m.