Triple

T20092130
Position Surface form Disambiguated ID Type / Status
Subject Zgierz E496296 entity
Predicate locatedOn P40 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: [Zgierz, locatedOn, Bzura River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bzura River
Context triple: [Zgierz, locatedOn, 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. Bystra River
    The Bystra River is a small watercourse in eastern Poland that flows through the spa town of Nałęczów and its surrounding countryside.
  • C. 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.
  • D. 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.
  • E. Pyszna River
    The Pyszna River is a small watercourse in central Poland that flows through the town of Wieluń and its surrounding 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66668db8881908c43b1deef9af1d3 completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:22 p.m.