Triple

T14758474
Position Surface form Disambiguated ID Type / Status
Subject Monthermé E346792 entity
Predicate river P165 FINISHED
Object Semois E66774 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: Semois | Statement: [Monthermé, river, Semois]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Semois
Context triple: [Monthermé, river, Semois]
  • A. Semois River chosen
    The Semois River is a picturesque waterway in southern Belgium and northern France, known for winding through the rugged, forested landscapes of the Ardennes.
  • B. Aube River
    The Aube River is a major waterway in northeastern France that flows through the Champagne region before joining the Seine.
  • C. Nièvre
    Nièvre is a rural department in central France’s Bourgogne-Franche-Comté region, known for its rolling countryside, the Loire River, and its capital city Nevers.
  • D. Saône River
    The Saône River is a major waterway in eastern France that flows through cities like Lyon and Dijon before joining the Rhône River.
  • E. Sambre
    The Sambre is a major river in northern France and southern Belgium that flows through the Walloon region before joining the Meuse at Namur.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7f0f5a48190af008352c26574d7 completed April 14, 2026, 11:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fef885b07c8190af5e33303af9fbea completed May 9, 2026, 9:04 a.m.
Created at: April 10, 2026, 1:30 a.m.