Triple
T32983723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Újszeged district |
E843878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Szeged |
C61141
|
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 Szeged Context triple: [Újszeged district, instanceOf, district of Szeged]
-
A.
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.
-
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.
town in Hungary
A town in Hungary is an urban settlement with local administrative authority, typically smaller than a city, that serves as a regional center for housing, services, and economic activities within the country.
-
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.
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.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.