Triple
T114042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser Poland Voivodeship |
E2305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative region |
C740
|
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: administrative region Context triple: [Lesser Poland Voivodeship, instanceOf, administrative region]
-
A.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
B.
region
A region is a bounded area within a larger space, defined by shared characteristics, properties, or relationships that distinguish it from surrounding areas.
-
C.
census region
A census region is a large geographic area defined by a statistical agency, grouping together multiple states or administrative units for the purpose of organizing, analyzing, and reporting population and economic data.
-
D.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.