Triple

T9813679
Position Surface form Disambiguated ID Type / Status
Subject Saar River E238341 entity
Predicate flowsInto P408 FINISHED
Object Moselle River at Konz E729646 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: Moselle River at Konz | Statement: [Saar River, flowsInto, Moselle River at Konz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moselle River at Konz
Context triple: [Saar River, flowsInto, Moselle River at Konz]
  • A. Moselle at Konz chosen
    Moselle at Konz is the section of the Moselle River near the town of Konz in western Germany where it meets and merges with the Saar River.
  • B. Moselle River
    The Moselle River is a major European waterway flowing through France, Luxembourg, and Germany, renowned for its scenic valleys and wine-producing regions.
  • C. Moselle
    Moselle is a department in northeastern France, bordering Germany and Luxembourg, known for its strategic location, industrial history, and mixed French-German cultural heritage.
  • D. Merzig
    Merzig is a town in the Saarland region of western Germany, near the borders with France and Luxembourg.
  • E. Saar River
    The Saar River is a major river in northeastern France and western Germany that flows through the industrial region of Saarland before joining the Moselle.
  • 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_69ca84defac48190abc1148804f184c1 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb22410208190b82b81a4df800f80 completed April 2, 2026, 12:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1cc67db68819093217c9a74e72fbf completed April 5, 2026, 2:43 a.m.
Created at: March 30, 2026, 8:30 p.m.