Triple

T17644603
Position Surface form Disambiguated ID Type / Status
Subject Battle of Benevento E429323 entity
Predicate location P40 FINISHED
Object Benevento 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: Benevento | Statement: [Battle of Benevento, location, Benevento]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Benevento
Context triple: [Battle of Benevento, location, Benevento]
  • A. Beneventum chosen
    Beneventum was an important ancient Roman city in southern Italy, strategically located as a key junction on major roads and known for its military and commercial significance.
  • B. Caserta
    Caserta is a city in southern Italy’s Campania region, best known for its grand 18th-century Royal Palace (Reggia di Caserta), a UNESCO World Heritage Site.
  • C. Pisae
    Pisae is the ancient Roman name for the city of Pisa in Tuscany, Italy, historically significant as a coastal settlement and later a prominent maritime republic.
  • D. Aversa
    Aversa is a historic city in southern Italy’s Campania region, known for its medieval origins and proximity to Naples.
  • E. Minturno
    Minturno is a historic town in the Lazio region of central Italy, known for its ancient Roman ruins and scenic position near the Tyrrhenian coast.
  • 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46de7da4881908d67f447910dba2f completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 6:04 a.m.