Triple

T22435091
Position Surface form Disambiguated ID Type / Status
Subject Val Montjoie E554599 entity
Predicate mainRiver P165 FINISHED
Object Bon-Nant 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: Bon-Nant | Statement: [Val Montjoie, mainRiver, Bon-Nant]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bon-Nant
Context triple: [Val Montjoie, mainRiver, Bon-Nant]
  • A. Bon Nant chosen
    Bon Nant is a mountain stream in the French Alps that flows through the Montjoie Valley before joining the Arve River.
  • B. Montboudifoise
    Montboudifoise is the French demonym referring to a female inhabitant or native of the commune of Montboudif in France.
  • C. Mont Dauban
    Mont Dauban is the tallest mountain on Silhouette Island in the Seychelles, known for its lush tropical forests and panoramic views over the Indian Ocean.
  • D. Balme
    Balme is a small alpine village in Italy’s Lanzo Valleys, known for its mountainous scenery and traditional mountain culture.
  • E. Vantoux
    Vantoux is a small French commune located in the Moselle department in northeastern France, near the city of Metz.
  • 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15adda0e48190825a5b705ae52d5b completed April 29, 2026, 1:11 a.m.
Created at: April 16, 2026, 8:47 p.m.