Triple

T11470592
Position Surface form Disambiguated ID Type / Status
Subject Emilia E271894 entity
Predicate namedAfter P63 FINISHED
Object Via Emilia E38023 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 Emilia | Statement: [Emilia, namedAfter, Via Emilia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Via Emilia
Context triple: [Emilia, namedAfter, Via Emilia]
  • A. Via Aemilia chosen
    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.
  • B. 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.
  • C. Via Flaminia
    Via Flaminia was a major ancient Roman consular road that connected Rome to the Adriatic Sea, serving as a crucial route for military, commercial, and administrative travel in central Italy.
  • D. Via Domitia
    Via Domitia was an ancient Roman road that linked Italy to Hispania across southern Gaul, serving as a major military and commercial route in the Roman Empire.
  • 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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d82949e3688190b024a4980666c94f completed April 9, 2026, 10:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69e6042507c4819096afc2839fda186d completed April 20, 2026, 10:47 a.m.
Created at: April 8, 2026, 9:35 p.m.