Triple

T13761500
Position Surface form Disambiguated ID Type / Status
Subject Ancient Roman nomen E330619 entity
Predicate example P1259 FINISHED
Object Domitius E1032501 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Domitius | Statement: [Ancient Roman nomen, example, Domitius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Domitius
Context triple: [Ancient Roman nomen, example, Domitius]
  • A. Domitius chosen
    Domitius is a Roman nomen (family name) associated with the ancient plebeian gens Domitia.
  • B. Quintianus
    Quintianus is a Roman cognomen derived from the praenomen Quintus, typically indicating familial or ancestral association with someone bearing that name.
  • C. Lucius Cestius
    Lucius Cestius was an ancient Roman figure, likely a magistrate or builder, commemorated as the namesake of the historic Ponte Cestio bridge in Rome.
  • D. Ianus Bifrons
    Ianus Bifrons is a title of the Roman god Janus emphasizing his two-faced aspect, symbolizing his role as guardian of transitions, beginnings, and endings.
  • E. Lucilius Bassus
    Lucilius Bassus was a 1st-century Roman general who played a key role in suppressing the Jewish Revolt under Emperor Vespasian.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d81c573f288190aa2403d484fa3d49 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02250f4881908d5193b3d5d25844 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7b06faed88190abc44e6256cb9301 completed May 3, 2026, 8:30 p.m.
Created at: April 9, 2026, 10:09 p.m.