Triple

T16955158
Position Surface form Disambiguated ID Type / Status
Subject Fonsomme E411280 entity
Predicate riverSourceOf P4102 FINISHED
Object Somme River E83858 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: Somme River | Statement: [Fonsomme, riverSourceOf, Somme River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Somme River
Context triple: [Fonsomme, riverSourceOf, Somme River]
  • A. Somme River chosen
    The Somme River is a waterway in northern France that became historically significant as the site of one of World War I’s largest and bloodiest battles.
  • B. Marne
    Marne is a department in northeastern France known for its Champagne-producing vineyards and historic towns such as Reims and Châlons-en-Champagne.
  • C. Marne
    The Marne is a major river in northeastern France that flows through the Île-de-France region before joining the Seine near Paris.
  • D. Marne
    Marne is a small city located in Cass County in the southwestern part of the U.S. state of Iowa.
  • E. Albert, Somme
    Albert, Somme is a small town in northern France that served as a key logistical and front-line center during the Battle of the Somme in World War I.
  • 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.