Triple

T1761813
Position Surface form Disambiguated ID Type / Status
Subject Latium E38673 entity
Predicate contains P35 FINISHED
Object Antium E66880 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: Antium | Statement: [Latium, contains, Antium]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Antium
Context triple: [Latium, contains, Antium]
  • A. Antium chosen
    Antium was an ancient coastal town in Latium, Italy, notable as a resort and birthplace of several Roman emperors, including Caligula and Nero.
  • B. Rhegium
    Rhegium was an important ancient Greek colony in southern Italy, located at the Strait of Messina and known for its strategic and commercial significance in Magna Graecia.
  • C. Clusium
    Clusium was an important ancient Etruscan city, known for its strategic location in central Italy and its significant role in early Roman history.
  • D. Arpinum
    Arpinum is an ancient Italian town in Latium best known as the birthplace of the Roman statesman and orator Cicero.
  • E. Falisci
    The Falisci were an ancient Italic people of central Italy, closely related to the Etruscans and known for their distinctive language and culture centered around the city of Falerii.
  • 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_69a8862d562481908d7025a1c1f67c0d completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa6463ac0081909e9ebe6ebf1db857 completed March 6, 2026, 5:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69adeacc64808190976d4a604d7762ea completed March 8, 2026, 9:31 p.m.
Created at: March 4, 2026, 7:31 p.m.