Triple
T29787501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huguenot consistory of Saumur |
E756303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Reformed church consistory |
C27480
|
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: Reformed church consistory Context triple: [Huguenot consistory of Saumur, instanceOf, Reformed church consistory]
-
A.
Reformed synod
A Reformed synod is an official governing assembly of ministers and elders within Reformed churches that meets to deliberate, decide, and provide oversight on doctrinal, disciplinary, and organizational matters.
-
B.
Reformed church building
A Reformed church building is a Christian worship structure designed and used by congregations within the Reformed (Calvinist) tradition, typically characterized by simple, unadorned architecture that emphasizes preaching and congregational gathering.
-
C.
Presbyterian church
A Presbyterian church is a Christian congregation organized under a representative form of governance by elders, emphasizing Reformed theology, preaching, sacraments, and communal worship.
-
D.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
-
E.
Kirchliches Gremium
chosen
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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:10 p.m.