Triple

T8618889
Position Surface form Disambiguated ID Type / Status
Subject Beneventum E204110 entity
Predicate traversedBy P225 FINISHED
Object Via Traiana E731737 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 Traiana | Statement: [Beneventum, traversedBy, Via Traiana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Via Traiana
Context triple: [Beneventum, traversedBy, Via Traiana]
  • A. Via Traiana chosen
    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.
  • B. Via Domitiana
    Via Domitiana was an ancient Roman road in southern Italy that linked important coastal and inland cities in the Campania region.
  • C. Via Claudia Augusta
    Via Claudia Augusta is an ancient Roman road that connected northern Italy with the provinces across the Alps, serving as a major transalpine trade and military route.
  • D. Via Appia
    Via Appia is one of the earliest and most important ancient Roman roads, historically serving as a major route connecting Rome to southern 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_69ca832ceab8819096e4a9f546695079 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc4712e74c81908b607a0ab2f9a361 completed March 31, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69cecc92beb48190ad406f48e58d9d0c completed April 2, 2026, 8:07 p.m.
Created at: March 30, 2026, 6:26 p.m.