Triple

T21557012
Position Surface form Disambiguated ID Type / Status
Subject Ennepetal (Gevelsberg) station E531918 entity
Predicate locatedOnRiver P165 FINISHED
Object Ennepe 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: Ennepe | Statement: [Ennepetal (Gevelsberg) station, locatedOnRiver, Ennepe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ennepe
Context triple: [Ennepetal (Gevelsberg) station, locatedOnRiver, Ennepe]
  • A. Ennepe chosen
    Ennepe is a river in North Rhine-Westphalia, Germany, that flows through the town of Ennepetal and serves as a tributary of the Ruhr.
  • B. Ahr River
    The Ahr River is a tributary of the Rhine in western Germany, known for flowing through the Eifel region and its surrounding wine-growing valleys.
  • C. Enkenbach
    Enkenbach is a locality in the German state of Rhineland-Palatinate, situated near Kaiserslautern and served by regional rail connections.
  • D. Elbbach
    Elbbach is a river in western Germany that flows through the town of Hadamar and is a tributary of the Lahn River.
  • E. Aschaff River
    The Aschaff River is a small river in Bavaria, Germany, that flows through the Spessart region before joining the Main River.
  • 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2e04b048190ac3a9913094b4625 completed April 27, 2026, 3:07 a.m.
Created at: April 16, 2026, 6:29 p.m.