Triple

T12063067
Position Surface form Disambiguated ID Type / Status
Subject Opole Voivodeship E287221 entity
Predicate containsCity P294 FINISHED
Object Wołczyn E413915 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: Wołczyn | Statement: [Opole Voivodeship, containsCity, Wołczyn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wołczyn
Context triple: [Opole Voivodeship, containsCity, Wołczyn]
  • A. Wołczyn chosen
    Wołczyn is a town in southwestern Poland historically notable as the birthplace of the last king of the Polish–Lithuanian Commonwealth, Stanisław II Augustus Poniatowski.
  • B. Wolyniec
    Wolyniec is a Polish-origin surname most notably associated with American soccer player and coach John Wolyniec.
  • C. Wilczyce
    Wilczyce is a village in southeastern Poland that serves as the seat of the rural administrative district Gmina Wilczyce in Sandomierz County.
  • D. Wojnowo
    Wojnowo is a village in western Poland that was formerly known by its German name Reckenwalde.
  • E. Władysławowo
    Władysławowo is a Polish seaside town and popular tourist resort on the Baltic coast, known for its beaches and fishing port.
  • 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_69d6ab4846e081908ee7bbd66a6d3459 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9043f82248190b05692aa0dc178a8 completed April 10, 2026, 2:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f654eb1881908d656009f1362ecf completed May 2, 2026, 1:04 p.m.
Created at: April 8, 2026, 9:48 p.m.