Triple

T22748581
Position Surface form Disambiguated ID Type / Status
Subject Park Miejski w Kaliszu E562625 entity
Predicate locatedOnRiver P165 FINISHED
Object Prosna 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: Prosna | Statement: [Park Miejski w Kaliszu, locatedOnRiver, Prosna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Prosna
Context triple: [Park Miejski w Kaliszu, locatedOnRiver, Prosna]
  • A. Prosna chosen
    Prosna is a river in western and central Poland that flows through cities such as Kalisz before joining the Warta River.
  • B. Pecica
    Pecica is a town in western Romania known for its archaeological sites and proximity to the Mureș River near the Hungarian border.
  • C. Potok
    Potok is a surname most notably associated with American Jewish author and rabbi Chaim Potok, known for novels exploring faith, identity, and tradition.
  • D. Bregava
    Bregava is a river in Bosnia and Herzegovina known for flowing through the town of Stolac before joining the Neretva River.
  • E. Sirok
    Sirok is a village in northern Hungary known for its medieval castle ruins and scenic location in the Mátra mountain region.
  • 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_69e24551ec7881909a9c924dbea155f6 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f179b822988190b5368ac1f4e1d70a completed April 29, 2026, 3:23 a.m.
Created at: April 17, 2026, 3:24 p.m.