Triple
T34953705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hauerland |
E1008069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German-speaking enclave |
C16129
|
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: German-speaking enclave Context triple: [Hauerland, instanceOf, German-speaking enclave]
-
A.
German exclave
A German exclave is a portion of German territory that is geographically separated from the main body of Germany and surrounded by foreign land or international waters.
-
B.
German-speaking area of Europe
chosen
The German-speaking area of Europe is the geographically and culturally defined region where German is a predominant or official language, including Germany, Austria, much of Switzerland, Liechtenstein, parts of Belgium, Luxembourg, Italy (South Tyrol), and some neighboring communities.
-
C.
German-speaking people
German-speaking people are individuals who use the German language as a primary or significant means of communication, sharing cultural, historical, and linguistic ties across various countries and regions.
-
D.
Swabian territory
Swabian territory is a historical and cultural region in southwestern Germany, traditionally associated with the Duchy of Swabia and characterized by its distinct Swabian dialect, customs, and shared regional identity.
-
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.
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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.