Triple
T37577182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Lutheran Council |
E934854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lutheran interchurch agency |
C31495
|
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: Lutheran interchurch agency Context triple: [National Lutheran Council, instanceOf, Lutheran interchurch agency]
-
A.
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.
-
B.
organ of the Lutheran World Federation
An organ of the Lutheran World Federation is an official governing or advisory body established by the Federation’s constitution to carry out specific leadership, decision-making, or administrative functions on its behalf.
-
C.
Lutheran church
A Lutheran church is a Christian congregation or building that follows the teachings of Martin Luther and the Lutheran Confessions, emphasizing salvation by grace through faith, the authority of Scripture, and liturgical worship.
-
D.
international Lutheran church association
chosen
An international Lutheran church association is a global fellowship that connects, supports, and coordinates Lutheran churches and ministries across different countries for shared mission, theology, and service.
-
E.
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.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.