Triple
T37834897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hont County |
E943311
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of the Kingdom of Hungary |
C39620
|
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 division of the Kingdom of Hungary Context triple: [Hont County, instanceOf, administrative division of the Kingdom of Hungary]
-
A.
administrative division of the Habsburg Monarchy
chosen
An administrative division of the Habsburg Monarchy was a territorial unit, such as a crown land, district, or province, established to organize governance, taxation, justice, and military administration within the multi-ethnic empire.
-
B.
district of Hungary
A district of Hungary is an administrative subdivision within a county that groups together several municipalities for local governance, statistical, and administrative purposes.
-
C.
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.
-
D.
county of Hungary
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.
-
E.
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.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.