Triple
T14462972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronicle of Hydatius |
E358631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late antique chronicle |
C8598
|
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: late antique chronicle Context triple: [Chronicle of Hydatius, instanceOf, late antique chronicle]
-
A.
Byzantine chronicle
A Byzantine chronicle is a historical narrative, often arranged annalistically, that records events of the Byzantine Empire and surrounding regions, typically blending factual reporting with religious interpretation and classical traditions.
-
B.
late antique historiographical work
chosen
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.
-
C.
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.
-
D.
verse chronicle
A verse chronicle is a historical or narrative account of real or legendary events told in the form of poetry, often arranged in chronological order.
-
E.
monastic chronicle
A monastic chronicle is a historical narrative compiled and maintained by monks within a religious community, recording significant events, religious observances, and local or wider affairs over time.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.