Triple
T24849377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myles Standish's 1623 Wessagusset expedition |
E621843
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in colonial American history |
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 American history Context triple: [Myles Standish's 1623 Wessagusset expedition, instanceOf, event in colonial American history]
-
A.
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.
-
B.
Revolutionary War event
A Revolutionary War event is a significant occurrence—such as a battle, political decision, treaty, or social upheaval—that directly influenced the course, conduct, or outcome of the American Revolutionary War.
-
C.
event in Native American history
A significant occurrence or series of actions involving Native American peoples that influenced their societies, cultures, territories, or relationships with other groups at a particular time in history.
-
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 during the 1675–1678 conflict between Native American tribes and English colonists in New England.
-
E.
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.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:20 a.m.