Triple
T33235780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council Chamber |
E850823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tudor court institution |
C48537
|
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 court institution Context triple: [Council Chamber, instanceOf, Tudor court institution]
-
A.
Tudor court
chosen
The Tudor court is the royal household and political center surrounding the Tudor monarchs of England, where power, patronage, ceremony, and intrigue shaped governance and culture in the 16th century.
-
B.
Tudor government position
A Tudor government position is an official role within the administrative, legal, or financial structures of England during the Tudor dynasty (1485–1603), responsible for implementing royal authority and managing state affairs.
-
C.
Tudor office
A Tudor office is a historical administrative or governmental position in England during the Tudor period, responsible for managing specific duties within the royal household, local governance, or national bureaucracy.
-
D.
Tudor-era noble
A Tudor-era noble is a high-ranking member of England’s aristocracy during the Tudor dynasty (1485–1603), wielding political influence, land-based wealth, and social prestige within a rigid hierarchical court and feudal system.
-
E.
Tudor monarch
A Tudor monarch is a ruler from the English royal House of Tudor (1485–1603), characterized by strong centralized authority, religious upheaval, and significant cultural and political transformation in England.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.