Triple

T17563828
Position Surface form Disambiguated ID Type / Status
Subject Arretium E427757 entity
Predicate connectedBy P37 FINISHED
Object Via Clodia NE NERFINISHED

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: Via Clodia | Statement: [Arretium, connectedBy, Via Clodia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Via Clodia
Context triple: [Arretium, connectedBy, Via Clodia]
  • A. Via Clodia chosen
    Via Clodia was an ancient Roman road that ran through Etruria, connecting Rome with various towns in central Italy.
  • B. Via Caecilia
    Via Caecilia was an ancient Roman road that connected central Italian settlements, facilitating military movement and trade across the region.
  • C. Via Popilia
    Via Popilia was an ancient Roman road that linked the city of Ariminum (modern Rimini) with other key centers in northern Italy, facilitating military movement and trade.
  • D. Via Salaria
    Via Salaria is an ancient Roman road that historically connected Rome to the Adriatic Sea, serving as a major route for the transport of salt and other goods.
  • E. Via Annia
    Via Annia was an important ancient Roman road in northern Italy that linked key cities of the region, including Aquileia, and facilitated trade and military movement.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4592bde448190bf5ed2340440e2b7 completed April 19, 2026, 4:25 a.m.
Created at: April 10, 2026, 5:50 a.m.