Triple
T8132905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Cavendish, 1st Marquess of Newcastle-upon-Tyne |
E189895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royalist military commander |
C16279
|
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: royalist military commander Context triple: [William Cavendish, 1st Marquess of Newcastle-upon-Tyne, instanceOf, royalist military commander]
-
A.
Royalist general
chosen
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.
-
B.
Jacobite leader
A Jacobite leader is a political or military figure who actively supported and directed efforts to restore the exiled Stuart dynasty to the thrones of England, Scotland, and Ireland between the late 17th and mid-18th centuries.
-
C.
medieval military leader
A medieval military leader is a high-ranking commander responsible for organizing, directing, and inspiring armed forces in warfare during the Middle Ages, often balancing battlefield tactics with feudal, political, and religious obligations.
-
D.
royalist
A royalist is a person who supports a monarchy and advocates loyalty to a reigning king, queen, or royal family as the legitimate source of political authority.
-
E.
royalist resistance group
A royalist resistance group is an organized, often clandestine movement that actively opposes existing authorities or occupying powers in order to restore, preserve, or expand the power of a monarchy.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:35 p.m.