Triple
T5243641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Beaufort, Duke of Exeter |
E118405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval politician |
C16977
|
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: medieval politician Context triple: [Thomas Beaufort, Duke of Exeter, instanceOf, medieval politician]
-
A.
13th-century English politician
A 13th-century English politician was a medieval figure involved in the governance of England, often serving in roles such as a member of Parliament, royal administrator, or local official under the monarchy.
-
B.
late medieval ruler
A late medieval ruler is a sovereign who governed a kingdom or principality in Europe roughly between the 13th and 15th centuries, navigating feudal structures, emerging centralized authority, and complex dynastic, religious, and military conflicts.
-
C.
medieval philosopher
A medieval philosopher is a thinker from roughly the 5th to 15th centuries who used logical analysis, often within religious frameworks, to explore questions about reality, knowledge, ethics, and the divine.
-
D.
medieval philosopher
A medieval philosopher is a thinker from roughly the 5th to the 15th century who used logical analysis, often within a religious framework, to explore questions about reality, knowledge, ethics, and the divine.
-
E.
medieval polity
A medieval polity is a territorially based political entity of the Middle Ages—such as a kingdom, duchy, city-state, or principality—defined by overlapping authorities, personal allegiances, and often fragmented sovereignty rather than a centralized nation-state structure.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:49 p.m.