Triple
T32140961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of Munich and Freising |
E820901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical province in Germany |
C57884
|
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: ecclesiastical province in Germany Context triple: [Province of Munich and Freising, instanceOf, ecclesiastical province in Germany]
-
A.
church building in Germany
A church building in Germany is a religious structure, often historically and architecturally significant, designed for Christian worship and community gatherings within the German cultural and legal context.
-
B.
organ of the Evangelical Church in Germany
An organ of the Evangelical Church in Germany is a formal body or institution (such as a council, office, or governing board) that performs specific administrative, legislative, or spiritual functions within the church’s organizational structure.
-
C.
region of Germany
A region of Germany is a geographically and culturally distinct area within the country, often defined by historical boundaries, administrative divisions, or shared economic and social characteristics.
-
D.
region of Bavaria
A region of Bavaria is a geographically and administratively defined area within the German federal state of Bavaria, characterized by shared cultural, historical, and economic features.
-
E.
Lutheran diocese
A Lutheran diocese is an administrative and ecclesiastical district of the Lutheran Church, overseen by a bishop and comprising multiple congregations within a defined geographic area.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:30 a.m.