Triple
T11210660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lausus, chamberlain of Emperor Theodosius II |
E265295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial chamberlain |
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: imperial chamberlain Context triple: [Lausus, chamberlain of Emperor Theodosius II, instanceOf, imperial chamberlain]
-
A.
Lord Chamberlain of the Household
The Lord Chamberlain of the Household is the senior officer of the Royal Household responsible for overseeing ceremonial events, royal protocol, and the coordination of official engagements and state occasions.
-
B.
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.
-
C.
imperial court office
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.
-
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.
unit of the Royal Household
A unit of the Royal Household is an organizational subdivision responsible for specific administrative, ceremonial, or domestic functions that support the sovereign and the functioning of the royal court.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:30 p.m.