Triple

T12728636
Position Surface form Disambiguated ID Type / Status
Subject Blovice E304172 entity
Predicate locatedOn P40 FINISHED
Object Úslava 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: Úslava River | Statement: [Blovice, locatedOn, Úslava River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Úslava River
Context triple: [Blovice, locatedOn, Úslava River]
  • A. Úslava River chosen
    The Úslava River is a river in the Czech Republic that flows through the Plzeň Region before joining the Berounka River.
  • B. Tagliamento River
    The Tagliamento River is a major Alpine river in northeastern Italy known for its largely unaltered braided channel and important ecological value.
  • C. Tokositna River
    The Tokositna River is a glacially fed river in Alaska that drains the southern slopes of the Alaska Range, including areas near Denali, before joining the Susitna River system.
  • D. Kněžná River
    The Kněžná River is a small river in the Hradec Králové Region of the Czech Republic that flows through the town of Rychnov nad Kněžnou.
  • E. Lovat River
    The Lovat River is a waterway in northwestern Russia that flows through the Novgorod region before emptying into Lake Ilmen.
  • 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d964172490819080cd022ff8290b6e completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:25 p.m.