Triple
T9403226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Procopius |
E226525
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine historian |
C6890
|
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 historian Context triple: [Procopius, instanceOf, Byzantine historian]
-
A.
Byzantine scholar
chosen
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.
-
B.
Hellenistic historian
A Hellenistic historian is a scholar from the Hellenistic period who researched, interpreted, and wrote narrative accounts of past events, often blending empirical inquiry with literary and rhetorical techniques to explain political, military, and cultural developments.
-
C.
Roman historian
A Roman historian is a scholar or writer from ancient Rome who researched, recorded, and interpreted past events of Rome and its world, often blending factual reporting with rhetorical and moral commentary.
-
D.
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.
-
E.
Byzantine official
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.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:46 p.m.