Triple
T33926361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg |
E869762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | kirchenleitende Entscheidung |
C7182
|
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: kirchenleitende Entscheidung Context triple: [Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg, instanceOf, kirchenleitende Entscheidung]
-
A.
Kirchliches Gremium
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 authority
chosen
Ecclesiastical authority is the recognized power and jurisdiction exercised by religious officials or institutions to govern doctrine, discipline, and practice within a faith community.
-
C.
Rechtsgrundlage einer Landeskirche
Die Rechtsgrundlage einer Landeskirche ist das normative Fundament, das in Verfassung, Kirchenordnung und staatlichen Vereinbarungen ihre rechtliche Stellung, innere Ordnung, Aufgaben und Beziehungen zu Staat und Gesellschaft verbindlich regelt.
-
D.
ecclesiastic
An ecclesiastic is a member of the clergy or a religious official who performs sacred duties and oversees spiritual affairs within a religious institution.
-
E.
head of church
The head of church is the highest-ranking religious leader who holds ultimate spiritual authority and administrative responsibility over a particular Christian church or 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.