Triple

T2649395
Position Surface form Disambiguated ID Type / Status
Subject Battle of Beneventum E53860 entity
Predicate place P373 FINISHED
Object Beneventum E204110 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: Beneventum | Statement: [Battle of Beneventum, place, Beneventum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beneventum
Context triple: [Battle of Beneventum, place, Beneventum]
  • 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. Nursia
    Nursia is an ancient town in central Italy, historically significant as the birthplace of Saint Benedict and known today as Norcia.
  • C. Capua
    Capua is an ancient city in southern Italy that was a prominent center of the Oscan-speaking Samnites and later an important Roman ally and urban hub.
  • D. Vercelli
    Vercelli is a historic city in northern Italy’s Piedmont region, known for its medieval architecture and important role in rice cultivation.
  • E. Clusium
    Clusium was an important ancient Etruscan city, known for its strategic location in central Italy and its significant role in early Roman history.
  • 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_69ab495e192081909c77b622e8e7e15a completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd91ca1288190ba302b04bac4c153 completed March 7, 2026, 7:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69af98cc2d9881908556b915a1870c02 completed March 10, 2026, 4:06 a.m.
Created at: March 6, 2026, 9:53 p.m.