Triple
T4091270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bács-Bodrog County |
E87708
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of the Kingdom of Hungary |
C8571
|
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: subdivision of the Kingdom of Hungary Context triple: [Bács-Bodrog County, instanceOf, subdivision of the Kingdom of Hungary]
-
A.
institution of the Kingdom of Hungary
An institution of the Kingdom of Hungary is an organized body or establishment—political, legal, religious, educational, or administrative—that operated within and under the authority of the historical Kingdom of Hungary.
-
B.
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.
-
C.
county of Hungary
chosen
A county of Hungary is a primary administrative division of the country, functioning as a regional unit of local government that coordinates municipalities and delivers public services within its territory.
-
D.
county of Hungary
A county of Hungary is a primary administrative territorial unit of the country, responsible for regional governance, public administration, and coordination of local municipalities within its boundaries.
-
E.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.