Triple

T15838598
Position Surface form Disambiguated ID Type / Status
Subject Faßberg E384043 entity
Predicate locatedNear P294 FINISHED
Object river Örtze E833240 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: river Örtze | Statement: [Faßberg, locatedNear, river Örtze]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: river Örtze
Context triple: [Faßberg, locatedNear, river Örtze]
  • A. Örtze River chosen
    The Örtze River is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
  • B. Zschopau River
    The Zschopau River is a tributary of the Freiberger Mulde in Saxony, Germany, flowing through the Ore Mountains and several towns before joining larger river systems.
  • C. River Mulde
    The River Mulde is a river in central Germany that flows through the states of Saxony and Saxony-Anhalt before joining the Elbe.
  • D. Rüdnitz
    Rüdnitz is a small municipality in the Barnim district of the federal state of Brandenburg in northeastern Germany.
  • 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 (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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142e4fa24819086a1a226082ac2d3 completed April 16, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00d447f5cc81908757869f2d1e94a1 completed May 10, 2026, 6:54 p.m.
Created at: April 10, 2026, 4:49 a.m.