Triple

T16955172
Position Surface form Disambiguated ID Type / Status
Subject Fonsomme E411280 entity
Predicate hasNameInLanguage P15 FINISHED
Object Fonsomme (French) E411280 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: Fonsomme (French) | Statement: [Fonsomme, hasNameInLanguage, Fonsomme (French)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fonsomme (French)
Context triple: [Fonsomme, hasNameInLanguage, Fonsomme (French)]
  • A. Fonsomme chosen
    Fonsomme is a commune in northern France notable as the place where the Somme River originates.
  • B. Thielle (French)
    Thielle is the French name for the Zihl, a river and canal system in western Switzerland connecting Lakes Neuchâtel and Biel.
  • C. La Bresse (French)
    La Bresse (French) is a commune in the Vosges department of northeastern France, known for its ski resort and outdoor mountain activities in the Vosges Mountains.
  • D. Montcresson (French)
    Montcresson (French) is a commune in north-central France, located in the Loiret department of the Centre-Val de Loire region.
  • E. Tessin (French)
    Tessin is the French name for the Swiss canton of Ticino, an Italian-speaking region in southern Switzerland.
  • 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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d01bb700819082a441c124be3cb6 completed April 18, 2026, 6:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00d464762c8190a734ffdd83633f70 completed May 10, 2026, 6:54 p.m.
Created at: April 10, 2026, 5:31 a.m.