Triple

T12064017
Position Surface form Disambiguated ID Type / Status
Subject Berounka River E287246 entity
Predicate hasRightTributary P415 FINISHED
Object Rakovník Stream E695961 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: Rakovník Stream | Statement: [Berounka River, hasRightTributary, Rakovník Stream]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rakovník Stream
Context triple: [Berounka River, hasRightTributary, Rakovník Stream]
  • A. Čáslavka stream
    Čáslavka stream is a small watercourse in the Czech Republic that flows through and gives its name to the town of Čáslav.
  • B. Rakovník Creek chosen
    Rakovník Creek is a small watercourse in the Czech Republic that flows through and gives its name to the town of Rakovník.
  • C. Stradomka River
    The Stradomka River is a minor watercourse in southern Poland that flows through the Lesser Poland region before joining the Raba River.
  • D. Velika Paklenica stream
    Velika Paklenica stream is a mountain river in Croatia known for carving the dramatic Velika Paklenica canyon within Paklenica National Park.
  • E. Zlínský potok
    Zlínský potok is a small stream in the Czech Republic that flows through and gives its name to the city of Zlín.
  • 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_69d6ab4846e081908ee7bbd66a6d3459 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90440dd988190ae2b80367aceb6f7 completed April 10, 2026, 2:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f654eb1881908d656009f1362ecf completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:48 p.m.