Triple

T6605178
Position Surface form Disambiguated ID Type / Status
Subject Battle of Ancona E149098 entity
Predicate location P40 FINISHED
Object Ancona E75439 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: Ancona | Statement: [Battle of Ancona, location, Ancona]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ancona
Context triple: [Battle of Ancona, location, Ancona]
  • A. Ancona chosen
    Ancona is a historic port city on Italy’s Adriatic coast, notable for its long-standing Jewish community and role as a commercial and cultural crossroads.
  • B. Rimini
    Rimini is a historic Italian coastal city on the Adriatic Sea, renowned for its beaches, Roman and Renaissance landmarks, and vibrant tourism industry.
  • C. Pescara
    Pescara is a coastal city in the Abruzzo region of central Italy, known for its Adriatic beaches, modern urban layout, and role as a commercial and tourist hub.
  • D. Pesaro
    Pesaro is a coastal city on Italy’s Adriatic Sea, known for its Renaissance architecture, seaside resorts, and as the birthplace of composer Gioachino Rossini.
  • E. Rovigo
    Rovigo is a small historic city in northeastern Italy known for its medieval architecture and location in the fertile Po River plain.
  • 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_69c687eaa7508190bb58ce2aa02039b3 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6af13151c81909b68fa6c77e1c482 completed March 27, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c70ae61a6481908158c3b7d58fd3ce completed March 27, 2026, 10:55 p.m.
Created at: March 27, 2026, 1:56 p.m.