Triple
T11210658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lausus, chamberlain of Emperor Theodosius II |
E265295
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine court official |
C6535
|
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: Byzantine court official Context triple: [Lausus, chamberlain of Emperor Theodosius II, instanceOf, Byzantine court official]
-
A.
Byzantine official
chosen
A Byzantine official is a government functionary of the Eastern Roman (Byzantine) Empire responsible for administering imperial policies, finances, justice, or military affairs within its complex bureaucratic hierarchy.
-
B.
Byzantine jurist
A Byzantine jurist is a legal scholar or judge of the Byzantine Empire who interpreted, applied, and commented on Roman and Byzantine law within the empire’s complex religious and imperial framework.
-
C.
Byzantine person
A Byzantine person is an individual who lived in or was culturally associated with the Byzantine Empire, characterized by its Eastern Roman heritage, Orthodox Christian faith, and rich traditions in art, law, and administration.
-
D.
Byzantine scholar
A Byzantine scholar is a learned individual specializing in the language, theology, history, and culture of the Byzantine Empire, often engaging in the preservation, interpretation, and commentary of classical and Christian texts.
-
E.
Byzantine noblewoman
A Byzantine noblewoman is an elite woman of the Eastern Roman Empire, distinguished by her high social rank, wealth, and influence within the imperial court, religious life, and family alliances.
- 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.