Triple

T21556540
Position Surface form Disambiguated ID Type / Status
Subject Histories E531906 entity
Predicate instanceOf P0 FINISHED
Object fragmentary historical work 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 work
Context triple: [Histories, instanceOf, fragmentary historical work]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. annalistic compilation
    An annalistic compilation is a chronological record that systematically arranges events year by year, often combining multiple sources to create a continuous historical narrative.
  • F. None of above. chosen

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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
Created at: April 16, 2026, 6:29 p.m.