Triple
T14698568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appian of Alexandria |
E345228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | chronicler of Roman history |
C13704
|
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: chronicler of Roman history Context triple: [Appian of Alexandria, instanceOf, chronicler of Roman history]
-
A.
Roman historian
chosen
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.
-
B.
Roman writer
A Roman writer is an individual from ancient Rome who composed literary, historical, philosophical, or rhetorical works in Latin or Greek, contributing to the cultural and intellectual life of the Roman world.
-
C.
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.
-
D.
Roman Empire scholar
A Roman Empire scholar is an expert who studies the history, culture, politics, society, and legacy of the Roman Empire through critical analysis of primary and secondary sources.
-
E.
Roman theologian
A Roman theologian is a scholar or cleric from ancient or medieval Rome who systematically studies, interprets, and teaches religious doctrines, particularly within the context of Roman religious or early Christian thought.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:28 a.m.