Triple
T10069314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Norris |
E213577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elizabethan military leader |
C22060
|
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: Elizabethan military leader Context triple: [John Norris, instanceOf, Elizabethan military leader]
-
A.
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.
-
B.
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.
-
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.
Tudor-period nobleman
chosen
A Tudor-period nobleman is a high-ranking member of the English aristocracy between 1485 and 1603, wielding political influence, land-based wealth, and social authority under the Tudor monarchy.
-
E.
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.
- 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 8:58 p.m.