Triple
T16561459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protestant Church of Augsburg Confession of Alsace and Lorraine |
E402348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional church |
C9317
|
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: regional church Context triple: [Protestant Church of Augsburg Confession of Alsace and Lorraine, instanceOf, regional church]
-
A.
Protestant regional church
chosen
A Protestant regional church is a territorially organized ecclesiastical body that unites Protestant congregations within a specific geographic area under shared governance, doctrine, and administrative structures.
-
B.
United Protestant regional church
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a shared governance, worship life, and mission.
-
C.
United Protestant regional church
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a common organizational and theological framework.
-
D.
particular Church
A particular Church is a local or regional Christian community, such as a diocese or eparchy, led by a bishop and fully sharing in the faith, sacraments, and governance of the universal Church.
-
E.
national church
A national church is a Christian church organization that is formally associated with, recognized by, or culturally identified as representing the religious life of a specific nation or state.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.