Triple
T13543874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL-UT |
E323461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographical subdivision code |
C3352
|
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: geographical subdivision code Context triple: [NL-UT, instanceOf, geographical subdivision code]
-
A.
geographic code
A geographic code is a standardized alphanumeric identifier used to represent specific geographic areas or locations for purposes such as mapping, analysis, and data organization.
-
B.
geographic location code
A geographic location code is a standardized alphanumeric identifier used to uniquely represent a specific physical area or place on Earth for mapping, analysis, and data exchange.
-
C.
ISO 3166-2 entry
chosen
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.
-
D.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
E.
geographical region
A geographical region is a defined area of the Earth's surface characterized by shared physical, cultural, political, or environmental features that distinguish it from surrounding areas.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:45 p.m.