Triple

T10289576
Position Surface form Disambiguated ID Type / Status
Subject Eschwege E241325 entity
Predicate locatedOn P40 FINISHED
Object Werra Valley E112665 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: Werra Valley | Statement: [Eschwege, locatedOn, Werra Valley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Werra Valley
Context triple: [Eschwege, locatedOn, Werra Valley]
  • A. Wuhle Valley
    Wuhle Valley is a river valley in Berlin, Germany, shaped by and named after the Wuhle River.
  • B. Saale River valley
    The Saale River valley is a scenic river landscape in central Germany characterized by winding waterways, steep slopes, and a mix of forests, vineyards, and historic towns.
  • C. Weser River valley
    The Weser River valley is a major geographical corridor in northwestern Germany, known for its scenic landscapes, historic towns, and role as an important route for transport and regional development.
  • D. Werra chosen
    The Werra is a major river in central Germany that forms one of the two headstreams of the Weser.
  • E. Wupper basin
    The Wupper basin is a river catchment area in North Rhine-Westphalia, Germany, drained by the Wupper River and encompassing several towns and cities in the Bergisches Land region.
  • 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_69d381aaafc08190af475ef58dc16aba completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2d192288190a64c27a4f26b71fc completed April 7, 2026, 9:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69d6f8556f4081908390bc5c14dcf560 completed April 9, 2026, 12:52 a.m.
Created at: April 6, 2026, 11:41 a.m.