Triple
T20245809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pressburg County |
E498421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | county of the Kingdom of Hungary |
C4791
|
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: county of the Kingdom of Hungary Context triple: [Pressburg County, instanceOf, county of the Kingdom of Hungary]
-
A.
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.
-
B.
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.
-
C.
institution of the Kingdom of Hungary
chosen
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.
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.
-
E.
administrative division of the Habsburg Monarchy
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.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:40 p.m.