Triple

T8374654
Position Surface form Disambiguated ID Type / Status
Subject Saar E197544 entity
Predicate flowsInto P408 FINISHED
Object Moselle 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 at Konz | Statement: [Saar, flowsInto, Moselle at Konz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moselle at Konz
Context triple: [Saar, flowsInto, Moselle 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. Mußbach
    Mußbach is a district of the wine-producing city Neustadt an der Weinstraße in Rhineland-Palatinate, Germany, known for its viticulture and scenic location along the German Wine Route.
  • C. Mosel, Germany
    Mosel, Germany is an industrial locality known for its major automotive manufacturing facilities, including a Volkswagen plant that produces models like the Passat.
  • D. Mondorf-les-Bains
    Mondorf-les-Bains is a spa town in southeastern Luxembourg renowned for its thermal baths, wellness facilities, and casino.
  • E. Rolandseck
    Rolandseck is a district of Remagen in Rhineland-Palatinate, Germany, known for its scenic location on the Rhine and its historic railway station and cultural venues.
  • 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_69ca82f56730819080cec5d991c76f4c completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb80a996ec819083ce2607c0cdab7f completed March 31, 2026, 8:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce02b4d840819090a0eaadaff9c9f9 completed April 2, 2026, 5:46 a.m.
Created at: March 30, 2026, 6:01 p.m.