Triple

T7023392
Position Surface form Disambiguated ID Type / Status
Subject Deva Victrix E162883 entity
Predicate instanceOf P0 FINISHED
Object Roman legionary fortress C6858 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: Roman legionary fortress
Context triple: [Deva Victrix, instanceOf, Roman legionary fortress]
  • A. Roman settlement
    A Roman settlement is a community established under Roman rule, characterized by Roman architecture, infrastructure, administration, and cultural practices integrated with local traditions.
  • B. Roman town
    A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
  • C. ancient Roman structure chosen
    An ancient Roman structure is a man-made construction from the Roman civilization, such as temples, amphitheaters, aqueducts, or baths, characterized by advanced engineering, arches, and durable materials like stone and concrete.
  • D. ancient Roman monument
    An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
  • E. Numidian settlement
    A Numidian settlement is a community or town established by the ancient Numidian people of North Africa, typically characterized by fortified hilltop locations, mixed pastoral-agricultural economies, and cultural influences from both indigenous Berber traditions and Mediterranean civilizations.
  • 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_69c6885b26248190a857541e3d10e299 completed March 27, 2026, 1:38 p.m.
Created at: March 27, 2026, 2:35 p.m.