Triple

T14569901
Position Surface form Disambiguated ID Type / Status
Subject Przemsza E341883 entity
Predicate formedByConfluenceOf P402 FINISHED
Object Black Przemsza E1083680 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: Black Przemsza | Statement: [Przemsza, formedByConfluenceOf, Black Przemsza]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Black Przemsza
Context triple: [Przemsza, formedByConfluenceOf, Black 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. Ruda
    Ruda is the former name of the global sportswear and athletic brand now known as Puma.
  • D. Ruda chosen
    Ruda is a river in southern Poland that flows through the Silesian region, including the city of Rybnik.
  • E. Praszka
    Praszka is a small town in southwestern Poland known for its location in the Opole region and its local industrial and cultural activities.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f2121481908f2385637944785d completed April 14, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8ac858108190b7c90130f18b0ddb completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:23 a.m.