Triple

T12420592
Position Surface form Disambiguated ID Type / Status
Subject Leverkusen E296756 entity
Predicate hasTwinTown P919 FINISHED
Object Racibórz E522024 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: Racibórz | Statement: [Leverkusen, hasTwinTown, Racibórz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Racibórz
Context triple: [Leverkusen, hasTwinTown, Racibórz]
  • A. Racibórz chosen
    Racibórz is a historic town in southern Poland, located in the Silesian region near the Czech border, known for its medieval heritage and industrial traditions.
  • B. Bolesławiec
    Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
  • C. Kluczbork
    Kluczbork is a town in southern Poland known as a local administrative, cultural, and economic center in the Opole region.
  • D. Zbrzyca
    Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
  • E. Glogów
    Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
  • 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_69d6ada0640c81908c061d7fb3d47786 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d6efd748190a5d9396a343e41e1 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a015fb168548190afb975ef60fa5f3e completed May 11, 2026, 4:48 a.m.
Created at: April 8, 2026, 9:55 p.m.