Triple
T37941857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burggrafenamt district (historical) |
E946508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former district of South Tyrol |
C66531
|
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: former district of South Tyrol Context triple: [Burggrafenamt district (historical), instanceOf, former district of South Tyrol]
-
A.
former province of Italy
A former province of Italy is an obsolete administrative division that once functioned as a mid-level local government unit within an Italian region, typically encompassing multiple municipalities before being reorganized or replaced.
-
B.
region of Austria
A region of Austria is a geographically defined area within the country characterized by shared administrative boundaries, cultural traits, economic activities, and natural features.
-
C.
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.
-
D.
administrative region of Bavaria
An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
-
E.
former canton of Switzerland
A former canton of Switzerland is a historical administrative region that once functioned as a semi-autonomous member state within the Swiss Confederation but has since been dissolved, merged, or reorganized.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.