Triple

T3289430
Position Surface form Disambiguated ID Type / Status
Subject Polybius’ Histories E69064 entity
Predicate instanceOf P0 FINISHED
Object historiographical work C13788 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: historiographical work
Context triple: [Polybius’ Histories, instanceOf, historiographical work]
  • A. historiographical theory
    Historiographical theory is the study of how history is written, interpreted, and constructed, examining the methods, assumptions, and perspectives that shape historical narratives.
  • B. historiographical tradition
    A historiographical tradition is a coherent, historically developed approach to interpreting and writing about the past, characterized by shared methods, assumptions, and narrative patterns among historians.
  • 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. work of intellectual history
    A work of intellectual history is a scholarly study that traces how ideas, theories, and systems of thought emerge, develop, and interact with their historical contexts over time.
  • 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_69ad859d45748190b0742408c954b39f completed March 8, 2026, 2:20 p.m.
Created at: March 8, 2026, 3:10 p.m.