Triple
T33926048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landessynode der Evangelischen Landeskirche in Württemberg |
E869754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | kirchenleitendes Gremium |
C27480
|
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: kirchenleitendes Gremium Context triple: [Landessynode der Evangelischen Landeskirche in Württemberg, instanceOf, kirchenleitendes Gremium]
-
A.
Kirchliches Gremium
chosen
Ein kirchliches Gremium ist eine organisierte Gruppe von Personen innerhalb einer Kirche, die gemeinsam Entscheidungen trifft, Beratungsaufgaben wahrnimmt oder bestimmte Verantwortungsbereiche in der kirchlichen Leitung und Verwaltung ausübt.
-
B.
ecclesiastical office-holding body
An ecclesiastical office-holding body is a formally constituted group within a religious organization that collectively holds, administers, or oversees specific church offices, duties, or authorities.
-
C.
group of clergy
A group of clergy is an organized body of ordained religious leaders who collectively perform spiritual, liturgical, and pastoral duties within a faith community.
-
D.
organ of a bishops’ conference
An organ of a bishops’ conference is a structured body or committee established by the conference to carry out specific functions such as governance, coordination, pastoral planning, or administration on behalf of the member bishops.
-
E.
denominational body
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.