Triple

T19264041
Position Surface form Disambiguated ID Type / Status
Subject Lake Skadar E481723 entity
Predicate inflow P415 FINISHED
Object Morača River 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: Morača River | Statement: [Lake Skadar, inflow, Morača River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morača River
Context triple: [Lake Skadar, inflow, Morača River]
  • A. Morača River chosen
    The Morača River is a major river in Montenegro that flows through the capital city of Podgorica before emptying into Lake Skadar.
  • B. Jošanica River
    The Jošanica River is a watercourse in southwestern Serbia that flows through the city of Novi Pazar and forms part of its local river system.
  • C. Malše River
    The Malše River is a river in Central Europe that flows through Austria and the Czech Republic, joining the Vltava River near the city of České Budějovice.
  • D. Butišnica River
    The Butišnica River is a watercourse in southern Croatia that flows through the Dalmatian hinterland near the town of Knin, contributing to the region’s karst landscape and local ecosystems.
  • E. Gračanka River
    The Gračanka River is a small watercourse in central Croatia that flows through the town of Gračanica and its surrounding area.
  • 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_69d8e8ce54cc8190998418ff1f66ef28 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fb8bce6881908395836960762672 completed April 20, 2026, 10:10 a.m.
Created at: April 10, 2026, 1:28 p.m.