Triple

T7924199
Position Surface form Disambiguated ID Type / Status
Subject Vlašim E184019 entity
Predicate locatedOn P40 FINISHED
Object Blanice River E866686 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: Blanice River | Statement: [Vlašim, locatedOn, Blanice River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Blanice River
Context triple: [Vlašim, locatedOn, Blanice River]
  • A. Blanice River chosen
    The Blanice River is a river in the Czech Republic that flows through the town of Vlašim and forms part of the Sázava River basin.
  • B. Prądnik River
    The Prądnik River is a small river in southern Poland known for carving the picturesque limestone valley that runs through Ojców and the surrounding Ojców National Park.
  • C. Wieprz River
    The Wieprz River is a major river in eastern Poland that flows through the Lublin region before joining the Vistula River.
  • D. Herkyna River
    The Herkyna River is a small river in central Greece historically associated with the ancient city and oracle of Lebadea (Lebadeia) in Boeotia.
  • E. Bîc River
    The Bîc River is a small river in Moldova that flows through the capital city of Chișinău before joining the Dniester.
  • 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_69ca828fe7bc819090f52c88dcd72183 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3aac02bc8190b13fc354a4fa91d3 completed March 31, 2026, 3:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69d90d3dfbac819087d07c35a1776064 completed April 10, 2026, 2:46 p.m.
Created at: March 30, 2026, 5:06 p.m.