Triple
T30873830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Box Elder Tabernacle |
E786417
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latter-day Saint meetinghouse |
C57729
|
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: Latter-day Saint meetinghouse Context triple: [Box Elder Tabernacle, instanceOf, Latter-day Saint meetinghouse]
-
A.
Mennonite meetinghouse
A Mennonite meetinghouse is a simple, unadorned building used by Mennonite congregations for worship, community gatherings, and religious instruction, reflecting their values of humility and plain living.
-
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.
Lutheran church building
A Lutheran church building is a Christian worship structure designed and used by a Lutheran congregation, typically featuring a simple, scripture-focused interior that reflects Lutheran theological and liturgical traditions.
-
D.
Latter-day Saint encampment
A Latter-day Saint encampment is a temporary gathering place where members of The Church of Jesus Christ of Latter-day Saints assemble—historically or in modern times—for worship, instruction, community building, and logistical organization during travel or large religious events.
-
E.
Christian chapel
A Christian chapel is a small, often intimate place of worship used for prayer, religious services, and sacraments within the Christian tradition.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:48 p.m.