Triple
T25903412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinando Fairfax |
E652680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Parliamentarian military commander |
C8929
|
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: Parliamentarian military commander Context triple: [Ferdinando Fairfax, instanceOf, Parliamentarian military commander]
-
A.
Parliamentarian general
chosen
A Parliamentarian general is a high-ranking military commander who leads and organizes armed forces on behalf of a parliamentary government, typically during periods of civil conflict or constitutional struggle.
-
B.
Nationalist commander
A nationalist commander is a military leader who directs armed forces in pursuit of a nation-centered political agenda, prioritizing national sovereignty, identity, and interests in strategy and operations.
-
C.
Military leader
A military leader is an individual who plans, directs, and coordinates armed forces operations, making strategic and tactical decisions to achieve military objectives while managing and motivating personnel under their command.
-
D.
Georgian military commander
A Georgian military commander is a high-ranking officer from Georgia responsible for planning, directing, and overseeing military operations and strategy within the Georgian armed forces.
-
E.
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.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:26 a.m.