Triple
T1512694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Underhill |
E32049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English colonial soldier |
C2241
|
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: English colonial soldier Context triple: [John Underhill, instanceOf, English colonial soldier]
-
A.
American colonial soldier
An American colonial soldier is an armed militiaman or regular enlisted in the British American colonies who participated in local defense, frontier warfare, and major conflicts such as the French and Indian War and the American Revolutionary War.
-
B.
English colonial settlement
An English colonial settlement is a community established by England in foreign territories during the age of exploration and empire, serving as a base for resource extraction, trade, and cultural expansion.
-
C.
European colonists
chosen
European colonists were settlers from various European nations who migrated to and established control over foreign lands, often displacing indigenous populations and exploiting local resources for economic and political gain.
-
D.
Loyalist
A Loyalist is an individual who steadfastly supports and defends a person, group, cause, or authority, often prioritizing allegiance and stability over change or personal gain.
-
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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.