Triple

T3504150
Position Surface form Disambiguated ID Type / Status
Subject Somme E74035 entity
Predicate containsRiver P165 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: [Somme, containsRiver, Somme River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Somme River
Context triple: [Somme, containsRiver, 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
    The Marne is a major river in northeastern France that flows through the Île-de-France region before joining the Seine near Paris.
  • C. Oise River
    The Oise River is a major waterway in northern France and southern Belgium that flows into the Seine and serves as an important route for inland navigation and commerce.
  • D. Semois River
    The Semois River is a picturesque waterway in southern Belgium and northern France, known for winding through the rugged, forested landscapes of the Ardennes.
  • E. Aube River
    The Aube River is a major waterway in northeastern France that flows through the Champagne region before joining the Seine.
  • 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbbf22b1c8190956141d8fb924210 completed March 8, 2026, 6:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4f018fe0481908291195f55fd765f completed March 14, 2026, 5:20 a.m.
Created at: March 8, 2026, 3:18 p.m.