Triple

T20641247
Position Surface form Disambiguated ID Type / Status
Subject Ourthe Orientale E507228 entity
Predicate hasNameInGerman P22792 FINISHED
Object Östliche Ourthe 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: Östliche Ourthe | Statement: [Ourthe Orientale, hasNameInGerman, Östliche Ourthe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Östliche Ourthe
Context triple: [Ourthe Orientale, hasNameInGerman, Östliche Ourthe]
  • A. Lorze River
    The Lorze River is a Swiss river in the canton of Zug, known for flowing through the Ägeri Valley and the Höllgrotten caves before joining the Reuss.
  • B. Trient River
    The Trient River is a mountain river in the Swiss Alps that flows through the Trient Valley before joining the Rhône.
  • C. Bregava River
    The Bregava River is a karst river in southern Bosnia and Herzegovina known for its clear waters, waterfalls, and historic stone bridges, particularly around the town of Stolac.
  • D. Örtze River
    The Örtze River is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
  • E. Oostelijke Ourthe chosen
    Oostelijke Ourthe is a river in the Belgian Ardennes that forms one of the two main headwaters of the Ourthe.
  • 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_69e0b4be702c8190a3d2410a881d310a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6ad132ebc8190b557914cf31a9033 completed April 20, 2026, 10:47 p.m.
Created at: April 16, 2026, 11:43 a.m.