Triple
T10681765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LWF Council |
E251773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organ of the Lutheran World Federation |
C28621
|
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: organ of the Lutheran World Federation Context triple: [LWF Council, instanceOf, organ of the Lutheran World Federation]
-
A.
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.
-
B.
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.
-
C.
organ of the Benedictine Confederation
An organ of the Benedictine Confederation is an official body or institution established within the Confederation to coordinate, support, or govern aspects of Benedictine monastic life across its autonomous congregations.
-
D.
Landeskirche
A Landeskirche is a regional Protestant church body in German-speaking countries, historically aligned with specific territories and often functioning as a semi-autonomous public-law institution within the broader national church structure.
-
E.
Landeskirche
A Landeskirche is a regional Protestant church body in German-speaking countries, organized along territorial lines and often historically linked to specific states or regions.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:10 p.m.