Triple

T6240525
Position Surface form Disambiguated ID Type / Status
Subject Battle of Arcole E139586 entity
Predicate near P350 FINISHED
Object Verona E118557 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: Verona | Statement: [Battle of Arcole, near, Verona]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Verona
Context triple: [Battle of Arcole, near, Verona]
  • A. Verona chosen
    Verona is a historic city in northern Italy renowned for its well-preserved Roman architecture and its association with Shakespeare’s "Romeo and Juliet."
  • B. Verona
    Verona is a small borough in Allegheny County, Pennsylvania, situated along the Allegheny River just northeast of Pittsburgh.
  • C. Padua
    Padua is a historic city in northern Italy renowned as a major cultural and academic center, home to one of Europe’s oldest universities.
  • D. Brescia
    Brescia is a historic industrial and cultural city in northern Italy, known for its Roman and medieval architecture and its role as an economic hub.
  • E. Pavia
    Pavia is a municipality in the Philippine province of Iloilo known for its suburban character and proximity to Iloilo City.
  • 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_69c008b1c5088190ae6de2555fc05ad8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063067d9c819085a18d9d03939266 completed March 22, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69c64ba0968c819091fae910b8c82879 completed March 27, 2026, 9:19 a.m.
Created at: March 22, 2026, 4:23 p.m.