Triple
T5365942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Goring, Lord Goring |
E103130
|
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: [George Goring, Lord Goring, 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.
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.
-
D.
British military leader
A British military leader is a high-ranking officer from the United Kingdom responsible for planning, directing, and overseeing military operations and strategy, often commanding troops in national defense or international conflicts.
-
E.
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.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 2:02 p.m.