Triple

T11407853
Position Surface form Disambiguated ID Type / Status
Subject Montgenèvre ski resort E270285 entity
Predicate locatedIn P40 FINISHED
Object Montgenèvre E55197 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: Montgenèvre | Statement: [Montgenèvre ski resort, locatedIn, Montgenèvre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Montgenèvre
Context triple: [Montgenèvre ski resort, locatedIn, Montgenèvre]
  • A. Montgenèvre chosen
    Montgenèvre is a French Alpine ski resort village in the Hautes-Alpes department, known for its high-altitude slopes and location near the Italian border.
  • B. Genolier
    Genolier is a small municipality in the canton of Vaud in western Switzerland, known for its scenic setting near Lake Geneva and the Jura Mountains.
  • C. Gueugnon
    Gueugnon is a small commune in eastern France known historically for its steel industry and location in the Bourgogne-Franche-Comté region.
  • D. Saignelégier
    Saignelégier is a municipality in the Swiss canton of Jura known for its rural landscapes, watchmaking heritage, and the annual Marché-Concours horse festival.
  • E. Faucigny
    Faucigny is a historical region in the French Alps that once formed part of the medieval domains of the Counts of Savoy.
  • 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_69d6aaddeaa8819088b30ef7b50598c9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8014e72748190a01bde2f0105cedb completed April 9, 2026, 7:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f08f0d9d0c8190a7b84e647c7491e9 completed April 28, 2026, 10:42 a.m.
Created at: April 8, 2026, 9:34 p.m.