Triple
T5868692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New England churches |
E130458
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic church tradition |
C5871
|
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: historic church tradition Context triple: [New England churches, instanceOf, historic church tradition]
-
A.
historic church body
A historic church body is a long-established Christian denomination or ecclesiastical organization whose identity, structure, and traditions have been shaped over centuries of continuous institutional and theological development.
-
B.
historic parish
A historic parish is a former ecclesiastical or civil territorial unit, typically centered around a church, whose boundaries and institutions reflect the administrative and social organization of a past period.
-
C.
event in church history
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
D.
medieval church
A medieval church is a religious building from the Middle Ages, typically characterized by stone construction, vaulted ceilings, stained glass windows, and architectural styles such as Romanesque or Gothic, serving as a center for worship and community life.
-
E.
Historic church
chosen
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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:56 p.m.