Triple
T27096612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Brant |
E686320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Loyalist military officer |
C52477
|
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: British Loyalist military officer Context triple: [John Brant, instanceOf, British Loyalist military officer]
-
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.
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.
-
C.
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.
-
D.
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.
-
E.
Royalist general
A Royalist general is a high-ranking military commander who leads armed forces in support of a monarchy, defending the authority and interests of the reigning royal family or crown.
- F. None of above. chosen
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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:44 a.m.