Triple
T5209009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Peter’s Episcopal Church (Chelsea, New York, work/alterations) |
E117583
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church renovation project |
C5246
|
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 renovation project Context triple: [St. Peter’s Episcopal Church (Chelsea, New York, work/alterations), instanceOf, church renovation project]
-
A.
architectural renovation project
chosen
An architectural renovation project is a coordinated effort to redesign, upgrade, and adapt an existing building or space to meet new functional, aesthetic, regulatory, and sustainability requirements while preserving or enhancing its structural integrity and character.
-
B.
former church
A former church is a building that was originally constructed and used for religious worship but has since been deconsecrated or repurposed for secular or alternative functions.
-
C.
architectural remodeling project
An architectural remodeling project is a coordinated effort to redesign, upgrade, or reconfigure an existing structure’s spaces, systems, and aesthetics to better meet current functional, regulatory, and stylistic requirements.
-
D.
court church
A court church is a Christian place of worship that is directly associated with and often located near a royal or princely court, serving the spiritual needs and ceremonial functions of the ruling household.
-
E.
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.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:47 p.m.