Triple
T26334529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Sheldon |
E662482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial militia leader |
C19773
|
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: colonial militia leader Context triple: [John Sheldon, instanceOf, colonial militia 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.
Williamite military leader
A Williamite military leader is a commander who supported and led armed forces on behalf of William III during the Williamite conflicts, particularly in the late 17th-century struggles over the English, Scottish, and Irish thrones.
-
C.
colonial commander
chosen
A colonial commander is a military leader responsible for overseeing, directing, and maintaining control over armed forces and local governance within a colony on behalf of an imperial power.
-
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.
military officer in the American Revolutionary War
A military officer in the American Revolutionary War is a commissioned leader responsible for organizing, commanding, and directing troops in combat and strategic operations during the conflict between the American colonies and Great Britain from 1775 to 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:35 p.m.