Triple
T10676143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hradec Králové District |
E251622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of the Czech Republic |
C28615
|
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: district of the Czech Republic Context triple: [Hradec Králové District, instanceOf, district of the Czech Republic]
-
A.
region of the Czech Republic
A region of the Czech Republic is a primary administrative territorial unit governed by a regional authority, encompassing multiple municipalities and serving as a framework for local governance, public services, and regional development.
-
B.
region of Slovakia
A region of Slovakia is an administrative territorial unit within the country, defined for governance, statistical, and organizational purposes, typically encompassing multiple districts and municipalities.
-
C.
district of Austria
A district of Austria is an administrative subdivision within a federal state that groups multiple municipalities for local governance, public administration, and regional services.
-
D.
district of Saxony
A district of Saxony is an administrative subdivision within the federal state of Saxony in Germany, responsible for local governance, public services, and regional planning across multiple municipalities.
-
E.
country in Central Europe
A country in Central Europe is a sovereign state located in the central part of the European continent, typically characterized by its landlocked or partially landlocked position and cultural, historical, and economic ties with neighboring European nations.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:09 p.m.