Triple
T24807680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justinianic commissioners |
E620697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine legal officials |
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 legal officials Context triple: [Justinianic commissioners, instanceOf, Byzantine legal officials]
-
A.
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.
-
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.
ancient Greek officials
Ancient Greek officials were public functionaries appointed or elected within the city-states to administer civic, religious, military, and judicial duties according to local laws and customs.
-
D.
Byzantine law code
A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
-
E.
Roman jurist
A Roman jurist was a legal expert in ancient Rome who interpreted, developed, and advised on Roman law, shaping its doctrines and practical application.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:50 a.m.