Triple

T19350482
Position Surface form Disambiguated ID Type / Status
Subject Haute-Vienne E484003 entity
Predicate namedAfter P63 FINISHED
Object Vienne River NE NERFINISHED

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: Vienne River | Statement: [Haute-Vienne, namedAfter, Vienne River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vienne River
Context triple: [Haute-Vienne, namedAfter, Vienne River]
  • A. Vienne River chosen
    The Vienne River is a major waterway in west-central France that flows through cities such as Limoges before joining the Loire.
  • B. Chiers River
    The Chiers River is a tributary of the Meuse that flows through Luxembourg, Belgium, and northeastern France, passing industrial towns such as Longwy along its course.
  • C. Trient River
    The Trient River is a mountain river in the Swiss Alps that flows through the Trient Valley before joining the Rhône.
  • D. Renous River
    The Renous River is a tributary waterway in New Brunswick, Canada, known for its salmon fishing and its confluence with the Southwest Miramichi River.
  • E. Ource River
    The Ource River is a small river in northeastern France that flows through the Champagne region, including the village of Essoyes, before joining the Seine.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d244f8819080eb1f3491300db2 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e6190381c081909c747a22422fb02c completed April 20, 2026, 12:16 p.m.
Created at: April 10, 2026, 1:34 p.m.