Triple
T6806813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salisbury, Massachusetts Bay Colony |
E156327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century town |
C21666
|
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: 17th-century town Context triple: [Salisbury, Massachusetts Bay Colony, instanceOf, 17th-century town]
-
A.
17th-century church
A 17th-century church is a religious building constructed in the 1600s that typically reflects Baroque or late Renaissance architectural styles, serving as a place of Christian worship and community gathering.
-
B.
17th-century movement
A 17th-century movement is a historically situated collective trend or initiative—cultural, intellectual, political, religious, or artistic—that emerged and developed primarily during the 1600s, shaping and reflecting the values and conflicts of that era.
-
C.
18th-century building
An 18th-century building is a structure constructed between 1701 and 1800 that typically reflects the architectural styles, materials, and construction techniques of that period, such as Georgian, Baroque, or Neoclassical design.
-
D.
17th-century person
A 17th-century person is an individual who lived during the 1600s, shaped by the political, religious, scientific, and cultural transformations of the early modern period.
-
E.
medieval city
A medieval city is a densely populated, fortified urban center characterized by narrow winding streets, defensive walls, a central marketplace, religious and administrative buildings, and distinct social and economic quarters.
- F. None of above. chosen
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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:16 p.m.