Triple
T25550703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformed Church of Beacon and surrounding area |
E640430
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church-related historic district |
C24185
|
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: church-related historic district Context triple: [Reformed Church of Beacon and surrounding area, instanceOf, church-related historic district]
-
A.
Historic church
A historic church is a long-standing religious building of significant architectural, cultural, and spiritual importance that reflects the beliefs, artistry, and community life of its era.
-
B.
historical district
chosen
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
-
C.
historical religious institution
A historical religious institution is an organized body or establishment that has played a significant role in shaping and preserving religious beliefs, practices, and cultural traditions over an extended period in history.
-
D.
Christian church complex
A Christian church complex is an integrated group of religious buildings and spaces, typically including a main church, auxiliary chapels, administrative and community facilities, and associated outdoor areas, dedicated to Christian worship, ministry, and communal life.
-
E.
historic peace church
A historic peace church is a Christian denomination with longstanding theological commitments to pacifism, nonviolence, and conscientious objection to war.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:36 p.m.