Triple
T31410658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Turner (colonial military officer) |
E801251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English colonial military officer |
C12490
|
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 military officer Context triple: [William Turner (colonial military officer), instanceOf, English colonial military officer]
-
A.
English colonial military leader
chosen
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.
British Loyalist military officer
A British Loyalist military officer is a commissioned leader who remained loyal to the British Crown during conflicts such as the American Revolutionary War, commanding Loyalist forces in support of British military objectives.
-
C.
English Civil War officer
An English Civil War officer is a commissioned military leader who commanded troops for either the Royalist or Parliamentarian forces during the mid-17th-century conflict in England.
-
D.
colonial officer
A colonial officer is an official appointed by a colonial power to administer, govern, and enforce its policies and interests within a colonized territory.
-
E.
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.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 8:38 p.m.