Triple

T9907093
Position Surface form Disambiguated ID Type / Status
Subject Rifugio Azzoni E185037 entity
Predicate locatedOn P40 FINISHED
Object Resegone E185037 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: Resegone | Statement: [Rifugio Azzoni, locatedOn, Resegone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Resegone
Context triple: [Rifugio Azzoni, locatedOn, Resegone]
  • A. Resegone chosen
    Resegone is a distinctive serrated mountain massif in the Bergamo Alps of northern Italy, overlooking the city of Lecco and famed for its saw-like ridgeline.
  • B. Resita
    Resita is an industrial city in western Romania, historically known for its steel production and heavy machinery manufacturing.
  • C. Reitoca
    Reitoca is a municipality in southern Honduras known for its rural character and location within the Francisco Morazán Department.
  • D. Resigaro
    Resigaro is an indigenous Arawakan language of the northwestern Amazon, traditionally spoken by a small community in the Peru–Brazil border region and now critically endangered.
  • E. Reola
    Reola is a village in Tartu County, Estonia, situated just south of the city of Tartu.
  • 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_69ca8296165881908ca4750701af1f29 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb50ec61481908f42bd2aa55d9a6e completed April 2, 2026, 12:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20daabd5881908b02da50a640766a completed April 5, 2026, 7:22 a.m.
Created at: March 30, 2026, 8:41 p.m.