Triple

T29411230
Position Surface form Disambiguated ID Type / Status
Subject Roman–Sabine relations E745898 entity
Predicate instanceOf P0 FINISHED
Object ancient Italo-Roman relations C55572 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 Italo-Roman relations
Context triple: [Roman–Sabine relations, instanceOf, ancient Italo-Roman relations]
  • A. settlement in ancient Italy
    A settlement in ancient Italy is a populated place such as a village, town, or city that existed on the Italian peninsula during antiquity, characterized by its social organization, infrastructure, and interaction with surrounding communities and cultures.
  • 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. Etruscan political organization
    Etruscan political organization consisted of independent city-states governed by powerful aristocratic elites and priest-kings, loosely united in a religious and political league that coordinated common interests without forming a centralized state.
  • D. area of ancient Rome
    An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
  • E. ancient Roman ally
    An ancient Roman ally is a foreign individual, city, or state that entered into a formal relationship with Rome—often through treaties or agreements—providing military or political support in exchange for protection, privileges, or limited autonomy.
  • 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_69f0a79eb7d081908c67197a5f347e68 completed April 28, 2026, 12:27 p.m.
Created at: April 28, 2026, 2:57 p.m.