Triple

T3402697
Position Surface form Disambiguated ID Type / Status
Subject Alban Hills E71692 entity
Predicate near P350 FINISHED
Object Via Appia E36820 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 Appia | Statement: [Alban Hills, near, Via Appia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Via Appia
Context triple: [Alban Hills, near, Via Appia]
  • A. Via Appia chosen
    Via Appia is one of the earliest and most important ancient Roman roads, historically serving as a major route connecting Rome to southern Italy.
  • 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 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.
  • D. 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.
  • 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_69ad85aac4808190a092c9cc8911f584 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb8e78ec8819089417666dc29f412 completed March 8, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69b35466945c8190b01aa016608415a0 completed March 13, 2026, 12:03 a.m.
Created at: March 8, 2026, 3:14 p.m.