Triple
T29865659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston revolt of 1689 |
E758449
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in colonial Massachusetts |
C383
|
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: event in colonial Massachusetts Context triple: [Boston revolt of 1689, instanceOf, event in colonial Massachusetts]
-
A.
history of a town in Massachusetts
A history of a town in Massachusetts is a chronological account of the town’s founding, development, key events, people, and transformations within the broader context of Massachusetts and New England history.
-
B.
colonial-era event
chosen
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
C.
event in King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred during the 1675–1678 conflict between Native American tribes and English colonists in New England.
-
D.
event in King Philip's War
An event in King Philip's War is a specific historical incident, battle, negotiation, or turning point that occurred between 1675 and 1678 during the conflict between Native American tribes and English colonists in New England.
-
E.
town in Massachusetts
A town in Massachusetts is a municipal entity with its own local government, typically governed by an open or representative town meeting and a board of selectmen, providing services and regulations for residents within its defined geographic boundaries.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:51 p.m.