Triple
T12546396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unity Synod |
E299979
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Moravian Church institution |
C8679
|
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: Moravian Church institution Context triple: [Unity Synod, instanceOf, Moravian Church institution]
-
A.
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.
-
B.
Orthodox Christian institution
An Orthodox Christian institution is an organized body, such as a church, monastery, or educational center, that preserves, practices, and transmits the faith, worship, and traditions of Eastern Orthodox Christianity within a structured communal framework.
-
C.
United Protestant regional church
chosen
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.
-
D.
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.
-
E.
Mennonite organization
A Mennonite organization is a faith-based group rooted in Anabaptist-Mennonite beliefs that coordinates religious, educational, service, or relief activities in alignment with Mennonite theology and community values.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.