Triple

T5670991
Position Surface form Disambiguated ID Type / Status
Subject Ludi Romani E124975 entity
Predicate instanceOf P0 FINISHED
Object Roman games C13466 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 games
Context triple: [Ludi Romani, instanceOf, Roman games]
  • A. Roman theatre
    A Roman theatre is a large, semi-circular open-air structure designed for public performances, featuring tiered seating, an orchestra, and an elaborately decorated stage building.
  • B. event in ancient Rome chosen
    An event in ancient Rome is a specific occurrence or happening—such as a political assembly, religious festival, public spectacle, or military action—situated in Roman society and time that holds social, cultural, or historical significance.
  • C. Roman art
    Roman art is the visual and architectural expression of ancient Rome, characterized by its adaptation of Greek models, emphasis on realism and portraiture, grand public monuments, and propagandistic function in service of the state and emperors.
  • D. 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.
  • E. client state of the Roman Empire
    A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
  • 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_69c00828906881908966f270b8f130cf completed March 22, 2026, 3:18 p.m.
Created at: March 22, 2026, 3:43 p.m.