Triple
T18831847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals of Fulda |
E460551
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin annals |
C34795
|
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: Latin annals Context triple: [Annals of Fulda, instanceOf, Latin annals]
-
A.
medieval Latin annals
chosen
Medieval Latin annals are chronological, year-by-year historical records written in Latin during the Middle Ages, typically noting significant political, religious, and natural events in brief entries.
-
B.
royal annals
Royal annals are chronological records maintained by or for a monarchy that document significant political, military, religious, and ceremonial events of a ruler’s reign.
-
C.
Roman historiography
Roman historiography is the body of historical writing produced in ancient Rome that blends factual record, rhetorical craft, and moral or political interpretation to narrate Rome’s past and shape its collective identity.
-
D.
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.
-
E.
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.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:56 a.m.