Triple
T3183643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockbridge Indian mission |
E66648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century religious community |
C6370
|
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: 18th-century religious community Context triple: [Stockbridge Indian mission, instanceOf, 18th-century religious community]
-
A.
former Shaker community
A former Shaker community is a once-active religious settlement founded by the Shakers that has since ceased functioning as an organized Shaker village but may retain historical buildings, cultural artifacts, and interpretive uses.
-
B.
religious settlement
chosen
A religious settlement is a community established and organized primarily around shared religious beliefs, practices, and institutions, often including places of worship and communal living arrangements.
-
C.
18th-century organization
An 18th-century organization is a formally or informally structured group of individuals operating during the 1700s to pursue political, economic, social, religious, or intellectual objectives within the historical context of early modern society.
-
D.
Anglican religious community
An Anglican religious community is a group of men or women within the Anglican tradition who live under a common rule of life, sharing prayer, worship, and service in a vowed or committed communal setting.
-
E.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.