Triple

T15031997
Position Surface form Disambiguated ID Type / Status
Subject Bug E378375 entity
Predicate flowsNear P350 FINISHED
Object Włodawa 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: Włodawa | Statement: [Bug, flowsNear, Włodawa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Włodawa
Context triple: [Bug, flowsNear, Włodawa]
  • A. Włodawa chosen
    Włodawa is a town in eastern Poland near the borders with Belarus and Ukraine, known for its multicultural heritage and proximity to the former Sobibor extermination camp.
  • B. Biała Podlaska
    Biała Podlaska is a city in eastern Poland near the Belarusian border, known as a local economic and cultural center of the Lublin Voivodeship.
  • C. Krasnystaw
    Krasnystaw is a town in eastern Poland known for its agricultural surroundings and annual Chmielaki beer and hops festival.
  • D. Pałuki
    Pałuki is a historical and ethnographic region in north-central Poland, known for its distinctive folk culture, wooden architecture, and numerous lakes.
  • E. Sieradz
    Sieradz is one of the oldest towns in central Poland, historically significant as a regional center and former royal city.
  • 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_69d85cd46b2c819090d054c27787f677 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7e2416081908dfba48d7f7b4a84 completed April 15, 2026, 12:12 a.m.
Created at: April 10, 2026, 2:59 a.m.