Triple

T20729876
Position Surface form Disambiguated ID Type / Status
Subject Emmendingen (district) E509544 entity
Predicate traversedBy P225 FINISHED
Object Dreisam (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: Dreisam (river) | Statement: [Emmendingen (district), traversedBy, Dreisam (river)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dreisam (river)
Context triple: [Emmendingen (district), traversedBy, Dreisam (river)]
  • A. Dreisam chosen
    Dreisam is a river in southwestern Germany that flows through the city of Freiburg im Breisgau and is known for shaping its landscape and recreational areas.
  • B. Saalach River
    The Saalach River is an Alpine river in Austria and Germany that flows through the spa town of Bad Reichenhall before joining the Salzach.
  • C. Aschaff River
    The Aschaff River is a small river in Bavaria, Germany, that flows through the Spessart region before joining the Main River.
  • D. Lachen River
    The Lachen River is a Himalayan mountain river in the Indian state of Sikkim, known for its glacial origins and role in feeding the Teesta River system.
  • E. Wiese River
    The Wiese River is a tributary of the Rhine flowing through parts of Germany and Switzerland, including the municipality of Riehen near Basel.
  • 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_69e0b4c589c08190834fb5d86d0efa2b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c1ec9820819093a07f90503686b2 completed April 21, 2026, 12:16 a.m.
Created at: April 16, 2026, 12:30 p.m.