Triple
T20815917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balatonfüred District |
E512436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Hungary |
C43790
|
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 Hungary Context triple: [Balatonfüred District, instanceOf, district of Hungary]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
district of Budapest
A district of Budapest is an administrative subdivision of Hungary’s capital city, each with its own local government, distinct neighborhoods, and specific urban, cultural, and historical characteristics.
-
E.
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.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:41 p.m.