Triple
T35032182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | domestikos ton scholon |
E1010810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine military office |
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 military office Context triple: [domestikos ton scholon, instanceOf, Byzantine military office]
-
A.
Roman military office
A Roman military office is an administrative and command position within the Roman armed forces responsible for organizing, directing, and managing soldiers, resources, and military operations.
-
B.
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.
-
C.
Byzantine noble title
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.
-
D.
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.
-
E.
Praetorian prefect
A Praetorian prefect was a high-ranking official in the Roman Empire who originally commanded the Praetorian Guard and later evolved into a powerful administrative and judicial authority overseeing major regions of the empire.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.