Triple
T30207260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine imperial chancery |
E767962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial chancery |
C4989
|
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: imperial chancery Context triple: [Byzantine imperial chancery, instanceOf, imperial chancery]
-
A.
imperial court office
chosen
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
B.
clerical chamber
A clerical chamber is a designated room or space where administrative, record-keeping, and other clerical tasks are performed, often within a larger institutional or religious setting.
-
C.
Inn of Chancery
An Inn of Chancery is a medieval English legal institution that served as a preparatory training house and residence for law students affiliated with the Inns of Court.
-
D.
clerk of the Privy Seal
A clerk of the Privy Seal was an official responsible for preparing, drafting, and processing documents that required authentication by the monarch’s privy seal, often serving as an intermediary between petitioners and higher offices of royal administration.
-
E.
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.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:31 p.m.