Triple

T3943191
Position Surface form Disambiguated ID Type / Status
Subject Passo Gavia E92082 entity
Predicate locatedNear P294 FINISHED
Object Ponte di Legno E402349 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: Ponte di Legno | Statement: [Passo Gavia, locatedNear, Ponte di Legno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ponte di Legno
Context triple: [Passo Gavia, locatedNear, Ponte di Legno]
  • A. Ponte di Legno chosen
    Ponte di Legno is an Italian alpine town and ski resort in Lombardy, known for its mountain scenery and outdoor sports tourism.
  • B. Ponte Bianco
    Ponte Bianco is a bridge in Trieste, Italy, spanning the city’s Canal Grande and connecting parts of its historic center.
  • C. Ponte Rosso
    Ponte Rosso is a historic bridge in Trieste, Italy, spanning the Canal Grande in the city’s central district.
  • D. Ponte di Paderno
    Ponte di Paderno is a historic iron railway and road bridge in northern Italy, renowned for its distinctive lattice structure spanning the Adda River.
  • E. Ponte Azzone Visconti
    Ponte Azzone Visconti is a historic multi-arched stone bridge in Lecco, Italy, dating back to the Middle Ages and notable for its strategic and architectural significance.
  • 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_69aed965502c8190904ebad1203a4ae8 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeedff736c8190b22e03d94c40f61a completed March 9, 2026, 3:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69b53ff66f348190bf054c7666cb16fc completed March 14, 2026, 11:01 a.m.
Created at: March 9, 2026, 3:24 p.m.