Triple
T26274474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Paul’s Episcopal Church, Philadelphia |
E660522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greek Revival church |
C8368
|
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: Greek Revival church Context triple: [St. Paul’s Episcopal Church, Philadelphia, instanceOf, Greek Revival church]
-
A.
Gothic Revival church
A Gothic Revival church is a Christian worship building designed in the 19th-century revival of medieval Gothic architecture, featuring pointed arches, ribbed vaults, and ornate tracery.
-
B.
Greek Revival building
chosen
A Greek Revival building is a structure designed in the early- to mid-19th-century architectural style that emulates classical Greek temples through features like tall columns, pediments, symmetrical facades, and bold, simple moldings.
-
C.
Renaissance-style church
A Renaissance-style church is a religious building characterized by symmetrical proportions, classical columns and pilasters, domes or central plans, and harmonious geometric order inspired by ancient Greco-Roman architecture.
-
D.
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.
-
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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 9:54 p.m.