Triple
T2987549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Slovakia |
E80662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Slovakia |
C12077
|
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: region of Slovakia Context triple: [Eastern Slovakia, instanceOf, region of Slovakia]
-
A.
historical region of Slovakia
A historical region of Slovakia is a geographically and culturally distinct area within the territory of present-day Slovakia that has developed its own identity, traditions, and administrative significance over the course of history.
-
B.
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.
-
C.
region of Hungary
A region of Hungary is a geographically defined area within the country characterized by shared administrative, cultural, economic, or historical features that distinguish it from other parts of Hungary.
-
D.
region of Poland
A region of Poland is a geographically and historically defined area within the country, often characterized by distinct cultural, economic, and administrative features.
-
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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:59 p.m.