Triple

T20497746
Position Surface form Disambiguated ID Type / Status
Subject Eisbachwelle E502917 entity
Predicate locatedOnWatercourse P1489 FINISHED
Object Eisbach 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: Eisbach | Statement: [Eisbachwelle, locatedOnWatercourse, Eisbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eisbach
Context triple: [Eisbachwelle, locatedOnWatercourse, Eisbach]
  • A. Eisbach chosen
    The Eisbach is a small, fast-flowing man-made river in Munich, Germany, famous for its standing wave that attracts urban surfers year-round.
  • B. Kraichbach
    Kraichbach is a small river in southwestern Germany that flows through the Kraichgau region before joining the Rhine.
  • C. Eckersbach
    Eckersbach is a district of the city of Zwickau in the German state of Saxony, known primarily as a residential area.
  • D. Kleinschwarzach
    Kleinschwarzach is a small locality that forms part of the municipality of Metten in Bavaria, Germany.
  • E. Langrickenbach
    Langrickenbach is a municipality in the canton of Thurgau in northeastern Switzerland, situated in a rural area near Lake Constance.
  • 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_69e0b4b0373881909dd3e9387f82eab4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69cbefe4c819098af5bfd4d92341d completed April 20, 2026, 9:38 p.m.
Created at: April 16, 2026, 11:35 a.m.