Triple

T12553063
Position Surface form Disambiguated ID Type / Status
Subject Charente E300141 entity
Predicate hasRiver P165 FINISHED
Object Vienne River E252485 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: Vienne River | Statement: [Charente, hasRiver, Vienne River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vienne River
Context triple: [Charente, hasRiver, 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. 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.
  • D. 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.
  • E. Omignon River
    The Omignon River is a small river in northern France that flows through the Hauts-de-France region before joining the Somme River.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9548444d081908f00cea1ce7032c7 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7b05474bc8190a42e2a9540055c47 completed May 3, 2026, 8:30 p.m.
Created at: April 8, 2026, 9:58 p.m.