Triple

T20976942
Position Surface form Disambiguated ID Type / Status
Subject Histories E516651 entity
Predicate instanceOf P0 FINISHED
Object ancient historical work C24614 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 historical work
Context triple: [Histories, instanceOf, ancient historical 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. 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.
  • D. ancient literary work chosen
    An ancient literary work is a written composition created in antiquity that reflects the language, culture, beliefs, and artistic expression of early civilizations.
  • E. historical reference work
    A historical reference work is a systematically organized resource that compiles verified information, dates, events, and interpretations about the past for quick consultation and scholarly use.
  • 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_69e0b4fee5ac8190875fa9ceba1a5e5e completed April 16, 2026, 10:07 a.m.
Created at: April 16, 2026, 1:47 p.m.