Triple
T9180991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Hopkins |
E220327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early American colonial leader |
C10375
|
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: early American colonial leader Context triple: [Stephen Hopkins, instanceOf, early American colonial leader]
-
A.
English colonial military leader
An English colonial military leader is a commander from England who directed armed forces and strategic operations in overseas colonies to expand, secure, or administer imperial control.
-
B.
Puritan statesman
A Puritan statesman is a political leader whose governance and public life are deeply shaped by Puritan religious principles, emphasizing moral rigor, communal discipline, and covenantal responsibility.
-
C.
colonist of the Thirteen Colonies
chosen
A colonist of the Thirteen Colonies is an inhabitant—often of European descent—who settled, lived, and participated in the social, economic, and political life of the British colonies in North America prior to and during the American Revolution.
-
D.
Revolutionary War leader
A Revolutionary War leader is an individual who organizes, commands, or significantly influences military and political efforts to overthrow an existing regime and establish a new order during a revolutionary conflict.
-
E.
American Revolutionary War figure
An American Revolutionary War figure is an individual who played a significant political, military, or ideological role in the struggle for independence of the thirteen American colonies from British rule between 1775 and 1783.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:23 p.m.