Triple

T16409894
Position Surface form Disambiguated ID Type / Status
Subject Brochów E398532 entity
Predicate locatedOnRiver P165 FINISHED
Object Bzura 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: Bzura River | Statement: [Brochów, locatedOnRiver, Bzura River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bzura River
Context triple: [Brochów, locatedOnRiver, Bzura River]
  • A. Bzura River chosen
    The Bzura River is a waterway in central Poland that gained historical significance as the site of a major World War II battle between Polish and German forces in 1939.
  • B. Bytowa River
    The Bytowa River is a small watercourse in northern Poland that flows through the town of Bytów and its surrounding Pomeranian landscape.
  • C. Kacza River
    The Kacza River is a small river in northern Poland that flows through the Gdynia district of Mały Kack into the Baltic Sea.
  • D. Pyszna River
    The Pyszna River is a small watercourse in central Poland that flows through the town of Wieluń and its surrounding region.
  • E. Dobra River
    The Dobra River is a picturesque river in Croatia known for its clear waters, karst landscapes, and importance to local ecosystems and recreation.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32871bce08190addd637413473c87 completed April 18, 2026, 6:45 a.m.
Created at: April 10, 2026, 5:09 a.m.