Triple

T33857052
Position Surface form Disambiguated ID Type / Status
Subject Origines E867811 entity
Predicate instanceOf P0 FINISHED
Object lost historical work C41019 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: lost historical work
Context triple: [Origines, instanceOf, lost historical work]
  • A. fragmentary historical work
    A fragmentary historical work is an incomplete surviving text from the past, preserved only in parts or quotations, that offers partial evidence about historical events, cultures, or authors.
  • B. lost text chosen
    Lost text is any written or recorded material that once existed but is now partially or completely unavailable due to destruction, disappearance, or incomplete preservation.
  • C. lost biblical source
    A lost biblical source is a hypothesized written document, no longer extant, that scholars infer once existed because later biblical texts appear to draw on its distinctive material or structure.
  • 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_69f349943ccc8190a3c41a3e0ae46cbf completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:47 a.m.