Triple
T32547097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | writings of Dexippus |
E831874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fragmentary historical works |
C44959
|
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: fragmentary historical works Context triple: [writings of Dexippus, instanceOf, fragmentary historical works]
-
A.
fragmentary historical work
chosen
A fragmentary historical work is an incomplete surviving text from the past, preserved only in parts or quotations, that offers partial evidence about historical events, cultures, or authors.
-
B.
historiographical work
A historiographical work is a scholarly study that analyzes how historical events, periods, or themes have been interpreted, debated, and written about by historians over time.
-
C.
work of narrative history
A work of narrative history is a factual account of past events told in a story-driven, literary style that emphasizes characters, chronology, and vivid detail while remaining grounded in historical evidence.
-
D.
section of historical work
A section of historical work is a distinct, thematically organized subdivision of a larger historical text that presents and analyzes specific events, periods, or topics within the broader narrative.
-
E.
late antique historiographical work
A late antique historiographical work is a narrative or analytical text composed between roughly the third and eighth centuries CE that interprets past events, often blending classical historical methods with emerging religious, political, and cultural perspectives of the period.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.