Triple

T879841
Position Surface form Disambiguated ID Type / Status
Subject Mont Blanc massif E19000 entity
Predicate near P350 FINISHED
Object Martigny E152398 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: Martigny | Statement: [Mont Blanc massif, near, Martigny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Martigny
Context triple: [Mont Blanc massif, near, Martigny]
  • A. Martigny chosen
    Martigny is a historic town in southwestern Switzerland known as a cultural and transportation hub in the canton of Valais, near the Great St. Bernard Pass.
  • B. Satigny
    Satigny is a Swiss municipality in the canton of Geneva, known for being one of the country’s largest wine-producing communes.
  • C. Delémont
    Delémont is a historic town in northwestern Switzerland that serves as the capital of the canton of Jura.
  • D. Cartigny
    Cartigny is a small rural municipality in western Switzerland known for its agricultural landscape and location within the canton of Geneva.
  • E. Chêne-Bougeries
    Chêne-Bougeries is a suburban municipality in western Switzerland, located just east of the city of Geneva in the canton of Geneva.
  • 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_69a4939c32488190a7ccd41cf0abb22b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4acc9d5f4819087afbb75b6ac3dbf completed March 1, 2026, 9:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad3ff724248190aacb72d105f0bb34 completed March 8, 2026, 9:23 a.m.
Created at: March 1, 2026, 7:39 p.m.