Triple
T6457695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Hatton |
E142034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elizabethan courtier |
C17127
|
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 courtier Context triple: [Christopher Hatton, instanceOf, Elizabethan courtier]
-
A.
royal courtier
A royal courtier is a member of a monarch’s household who attends the ruler, manages or influences court affairs, and advances political, social, or personal interests within the royal court.
-
B.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
-
C.
15th-century English politician
A 15th-century English politician is a historical figure who participated in the governance and political affairs of England during the 1400s, often through roles in Parliament, royal councils, or local administration.
-
D.
Renaissance figure
A Renaissance figure is a historically significant individual from roughly the 14th to 17th centuries who contributed to the revival of classical learning and the flourishing of arts, sciences, and humanist thought in Europe.
-
E.
16th-century politician
chosen
A 16th-century politician is a historical public figure who engaged in governance, policy-making, and power negotiations within the complex religious, dynastic, and imperial conflicts of the 1500s.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:48 p.m.