Triple
T12182242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königsboden |
E290248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Transylvanian Saxon settlement area |
C29922
|
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: Transylvanian Saxon settlement area Context triple: [Königsboden, instanceOf, Transylvanian Saxon settlement area]
-
A.
Moravian settlement
A Moravian settlement is a planned religious community established by the Moravian Church, characterized by communal living, shared economic enterprises, and a strong emphasis on worship, education, and missionary work.
-
B.
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.
-
C.
German minority in Romania
chosen
The German minority in Romania is an ethnic community historically composed of various German-speaking groups, such as Transylvanian Saxons and Banat Swabians, who settled in Romanian territories from the Middle Ages onward and have significantly influenced the region’s cultural, economic, and architectural development.
-
D.
Karelian settlement area
Karelian settlement area: A geographic region historically and currently inhabited by the Karelian people, characterized by their distinct language, culture, and traditional livelihoods.
-
E.
county of Romania
A county of Romania is an administrative territorial unit that serves as a primary subdivision of the country, encompassing multiple cities and communes under a local governing council and prefect.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:50 p.m.