Triple

T3943190
Position Surface form Disambiguated ID Type / Status
Subject Passo Gavia E92082 entity
Predicate locatedNear P294 FINISHED
Object Bormio E399491 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: Bormio | Statement: [Passo Gavia, locatedNear, Bormio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bormio
Context triple: [Passo Gavia, locatedNear, Bormio]
  • A. Bormio chosen
    Bormio is a historic alpine town in northern Italy renowned for its ski resorts, thermal baths, and proximity to major mountain passes in the Stelvio National Park.
  • B. Cortina d'Ampezzo
    Cortina d'Ampezzo is a renowned Italian Alpine resort town in the Dolomites, famous for skiing, mountaineering, and hosting major winter sports events.
  • C. Bardonecchia
    Bardonecchia is an alpine town in northwestern Italy known as a ski resort and transport hub near the French border in the Susa Valley.
  • D. Domodossola
    Domodossola is a town in northern Italy’s Piedmont region, historically situated in the territory once inhabited by the ancient Lepontii people.
  • E. Lecco
    Lecco is an Italian town in the Lombardy region, known for its scenic location at the southeastern tip of Lake Como and its surrounding Alpine foothills.
  • 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_69b556173f848190bf8b879a7c61a43f completed March 14, 2026, 12:35 p.m.
Created at: March 9, 2026, 3:24 p.m.