Triple

T12238980
Position Surface form Disambiguated ID Type / Status
Subject Jizera River E291676 entity
Predicate hasGermanName P1435 FINISHED
Object Iser E550648 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: Iser | Statement: [Jizera River, hasGermanName, Iser]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iser
Context triple: [Jizera River, hasGermanName, Iser]
  • A. Dyje
    The Dyje is a major river in Central Europe that flows through the Czech Republic and Austria, forming part of their border and contributing significantly to the Morava River basin.
  • B. Rissne
    Rissne is a residential district and urban area in the Stockholm metropolitan region of Sweden, known for its mix of apartment housing and proximity to public transit.
  • C. Örtze River
    The Örtze River is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
  • D. Labe chosen
    Labe, known internationally as the Elbe, is a major Central European river that flows from the Czech Republic through Germany to the North Sea.
  • E. Körös
    Körös is a river in Central Europe that flows through eastern Hungary and parts of Romania before joining the Tisza River.
  • 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_69d6ab67950c8190be08450a06228c4b completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cb45340819093365f8efdf85f75 completed April 10, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64b893a70819090d4ebb0609e6544 completed May 2, 2026, 7:07 p.m.
Created at: April 8, 2026, 9:51 p.m.