Triple
T7253392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Gods |
E157658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient scholarly work |
C9097
|
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: ancient scholarly work Context triple: [On the Gods, instanceOf, ancient scholarly work]
-
A.
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.
-
B.
late antique historiographical work
A late antique historiographical work is a narrative text composed between the third and eighth centuries CE that interprets past events—often blending classical, Christian, and local traditions—to construct meaning, identity, and authority for its contemporary audience.
-
C.
ancient literature
chosen
Ancient literature encompasses the written works, myths, epics, religious texts, and philosophical writings produced by early civilizations that reveal their cultures, beliefs, and historical experiences.
-
D.
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.
-
E.
scholarly publication
A scholarly publication is a formally written and peer-reviewed work that presents original research, analysis, or theoretical contributions to an academic field.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:56 p.m.