Triple
T9586545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Browne, Viscount Montagu |
E231304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tudor-period courtier |
C5196
|
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: Tudor-period courtier Context triple: [Anthony Browne, Viscount Montagu, instanceOf, Tudor-period courtier]
-
A.
Tudor-period nobleman
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.
-
B.
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.
-
C.
15th-century English noblewoman
A 15th-century English noblewoman is an aristocratic woman of late medieval England whose life centers on dynastic marriage, estate management, patronage, and navigating the political and social upheavals of the Wars of the Roses.
-
D.
royal courtier
chosen
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.
-
E.
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.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:06 p.m.