Triple

T19869535
Position Surface form Disambiguated ID Type / Status
Subject Wieluń County E477475 entity
Predicate capital P234 FINISHED
Object Wieluń 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: Wieluń | Statement: [Wieluń County, capital, Wieluń]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wieluń
Context triple: [Wieluń County, capital, Wieluń]
  • A. Wieluń chosen
    Wieluń is a town in south-central Poland historically known as one of the first targets of German aerial bombardment at the start of World War II.
  • B. Uniejów
    Uniejów is a historic spa town in central Poland, known for its medieval castle and geothermal thermal baths.
  • C. Muszyna
    Muszyna is a spa and tourist town in southern Poland, known for its mineral springs and scenic mountain surroundings near the Slovak border.
  • D. Wierzyca
    Wierzyca is a river in northern Poland that flows through the Pomeranian region before joining the Wda and ultimately contributing to the Vistula river basin.
  • E. Bukowiec
    Bukowiec is a village in southwestern Poland known for its scenic location in the Karkonosze foothills and historic park-and-palace complex.
  • 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_69d8e51e7d948190aedbcd6c30361c39 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e658a2cc8481908d134b0b5cf79d06 completed April 20, 2026, 4:47 p.m.
Created at: April 10, 2026, 1:51 p.m.