Triple

T10025307
Position Surface form Disambiguated ID Type / Status
Subject Altinum E200708 entity
Predicate locatedOn P40 FINISHED
Object Via Annia E830307 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: Via Annia | Statement: [Altinum, locatedOn, Via Annia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Via Annia
Context triple: [Altinum, locatedOn, Via Annia]
  • A. Via Annia chosen
    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.
  • B. Via Aemilia
    Via Aemilia was a major Roman consular road in northern Italy that connected key cities such as Ariminum (Rimini) and Placentia (Piacenza), fostering trade and military movement across the region.
  • C. Via Aemilia Scauri
    Via Aemilia Scauri was an important ancient Roman road that extended and complemented the coastal route of the Via Aurelia in Italy.
  • D. Via Traiana
    Via Traiana was an ancient Roman road built by Emperor Trajan to provide a shorter, more efficient route across southern Italy between Beneventum and the Adriatic coast.
  • E. Via Latina
    Via Latina was an important ancient Roman road that linked Rome with southern Italy, running through Latium and serving as a key military and commercial route.
  • 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_69ca831c45f08190ac1505cc15076608 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcd7d9c9c81909a0a0917deed0973 completed April 2, 2026, 1:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2cb9a62788190aed75d03f1d2aeb6 completed April 5, 2026, 8:52 p.m.
Created at: March 30, 2026, 8:53 p.m.