Triple

T13468325
Position Surface form Disambiguated ID Type / Status
Subject Wieprz River E311561 entity
Predicate connectedTo P37 FINISHED
Object Krzna River E381484 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: Krzna River | Statement: [Wieprz River, connectedTo, Krzna River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krzna River
Context triple: [Wieprz River, connectedTo, Krzna River]
  • A. Krzna River chosen
    The Krzna River is a significant river in eastern Poland that serves as one of the main tributaries of the Bug River, flowing through the Lublin region.
  • B. Huczwa River
    The Huczwa River is a tributary watercourse in eastern Poland that feeds into the Bug River and contributes to the region’s drainage system.
  • C. Kamenice River
    The Kamenice River is a river in the northern Czech Republic that flows through the Bohemian Switzerland region before joining the Jizera River.
  • D. Jizera River
    The Jizera River is a significant river in the Czech Republic that flows from the Jizera Mountains and serves as an important tributary of the Elbe River.
  • E. Orlice River
    The Orlice River is a significant river in the Czech Republic that flows through eastern Bohemia and joins the Elbe near the city of Hradec Králové.
  • 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf21e46081908a00c9acf54f270f completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6471ba348190a0cd1745daff6114 completed May 8, 2026, 4:20 a.m.
Created at: April 9, 2026, 9:42 p.m.