Triple
T28780900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobilissimus Caesar |
E726672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine honorific |
C48059
|
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 honorific Context triple: [Nobilissimus Caesar, instanceOf, Byzantine honorific]
-
A.
Byzantine noble title
chosen
A Byzantine noble title is a formal rank or honorific designation within the hierarchical aristocratic and court system of the Byzantine Empire, signifying status, authority, and often specific administrative or military responsibilities.
-
B.
ancient Roman title
An ancient Roman title is a formal designation or rank used in Roman society and government to denote an individual's official role, status, or authority within the political, military, religious, or social hierarchy.
-
C.
Mycenaean title
A Mycenaean title is an official designation or rank recorded in Linear B script that identifies the social, administrative, or religious role of an individual within Mycenaean society.
-
D.
honorific
An honorific is a title, word, or expression used to convey respect, deference, or social status when addressing or referring to a person.
-
E.
Byzantine ecclesiastical office
A Byzantine ecclesiastical office is a formal clerical position within the hierarchical structure of the Eastern Roman (Byzantine) Church, encompassing specific liturgical, administrative, and judicial duties tied to the empire’s religious and imperial governance.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:19 a.m.