Triple

T18907896
Position Surface form Disambiguated ID Type / Status
Subject Piovega E462513 entity
Predicate hasNeighbouringLocality P68061 FINISHED
Object Arzerello 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: Arzerello | Statement: [Piovega, hasNeighbouringLocality, Arzerello]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arzerello
Context triple: [Piovega, hasNeighbouringLocality, Arzerello]
  • A. Arzerello chosen
    Arzerello is a locality or frazione within the municipality of Piove di Sacco in the Veneto region of northern Italy.
  • B. Zoncolan
    Zoncolan is a notoriously steep mountain in the Italian Alps, famous as one of the toughest climbs in professional road cycling.
  • C. Ornavasso
    Ornavasso is a town in northern Italy notable for its rich archaeological remains linked to the ancient Lepontic Celtic culture.
  • D. Fagnano Alto
    Fagnano Alto is a small mountain village and comune in the Abruzzo region of central Italy, known for its scenic setting within the Apennines and traditional rural character.
  • E. Lomazzo
    Lomazzo is a town in northern Italy’s Lombardy region, situated between Como and Milan and known for its residential character and local industry.
  • 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_69d8dcfd05bc819088903cca13cc2846 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c52eed1881908929dace845ae008 completed April 20, 2026, 6:18 a.m.
Created at: April 10, 2026, 11:58 a.m.