Triple

T19183778
Position Surface form Disambiguated ID Type / Status
Subject Sachsenwald E469644 entity
Predicate traversedBy P225 FINISHED
Object river Bille 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: river Bille | Statement: [Sachsenwald, traversedBy, river Bille]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: river Bille
Context triple: [Sachsenwald, traversedBy, river Bille]
  • A. River Bille chosen
    River Bille is a small river in northern Germany that flows through Schleswig-Holstein and Hamburg before joining the Elbe.
  • B. river Bode
    The river Bode is a watercourse in the Harz Mountains of central Germany, known for its scenic valleys, gorges, and role in regional tourism and hydropower.
  • C. Vejle River
    Vejle River is a Danish watercourse in Jutland known for flowing through the town of Vejle and its surrounding valley before emptying into Vejle Fjord.
  • D. river Oker
    The river Oker is a watercourse in Lower Saxony, Germany, that flows from the Harz Mountains through towns such as Altenau before joining the Aller River.
  • E. Odense River
    The Odense River is a waterway on the Danish island of Funen that flows through the city of Odense before emptying into Odense Fjord.
  • 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_69d8dd0ad9088190a173b32657ae2e7a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f61f1d9c8190b67555383d821958 completed April 20, 2026, 9:47 a.m.
Created at: April 10, 2026, 12:07 p.m.