Triple

T31077447
Position Surface form Disambiguated ID Type / Status
Subject Curiosum Urbis Romae E792003 entity
Predicate instanceOf P0 FINISHED
Object ancient Roman document C45442 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 Roman document
Context triple: [Curiosum Urbis Romae, instanceOf, ancient Roman document]
  • A. Roman administrative text chosen
    A Roman administrative text is a written document produced by Roman authorities to record, regulate, or communicate matters of governance, such as laws, edicts, census data, tax records, and official correspondence.
  • B. ancient Roman
    An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
  • C. ancient Roman literature
    Ancient Roman literature encompasses the body of written works produced in Latin (and some Greek) by Roman authors, reflecting the political, social, philosophical, and artistic life of Rome from its early Republic through the Imperial period.
  • D. late Roman legal codex
    A late Roman legal codex is a formally compiled, systematically organized collection of imperial laws, juristic writings, and legal principles produced in the later Roman Empire to standardize and preserve authoritative legal practice.
  • E. 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.
  • 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_69f224ccdbbc81909b0cdb4cc2d70c7a completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:02 p.m.