Triple

T17849574
Position Surface form Disambiguated ID Type / Status
Subject Dąbrowa Górnicza E445760 entity
Predicate locatedOnRiver P165 FINISHED
Object Czarna Przemsza 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: Czarna Przemsza | Statement: [Dąbrowa Górnicza, locatedOnRiver, Czarna Przemsza]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Czarna Przemsza
Context triple: [Dąbrowa Górnicza, locatedOnRiver, Czarna Przemsza]
  • A. Czarnca
    Czarnca is a village in south-central Poland historically known as the birthplace and estate of the 17th-century Polish military commander Stefan Czarniecki.
  • B. Czarny Groń
    Czarny Groń is a mountain peak in southern Poland, located in the Maków Beskids range and known for its hiking and skiing opportunities.
  • C. Tyśmienica
    Tyśmienica is a river in eastern Poland that flows through the Lublin region before joining the Western Bug.
  • D. Czeladź
    Czeladź is a historic industrial town in southern Poland, located in the Silesian metropolitan area near Katowice.
  • E. Przemsza chosen
    Przemsza is a river in southern Poland formed by the confluence of the Black and White Przemsza, known historically as a regional border and an important tributary of the Vistula.
  • 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffd7e2c81909a42cc7ab64e7db9 completed April 19, 2026, 8:19 a.m.
Created at: April 10, 2026, 10:16 a.m.