Triple

T14180372
Position Surface form Disambiguated ID Type / Status
Subject Rybnik E351435 entity
Predicate hasRailwayConnectionTo P3791 FINISHED
Object Racibórz 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: Racibórz | Statement: [Rybnik, hasRailwayConnectionTo, Racibórz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Racibórz
Context triple: [Rybnik, hasRailwayConnectionTo, 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 (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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61ca3ad88190944850c97760dcbf completed April 14, 2026, 3:48 p.m.
Created at: April 10, 2026, 1:02 a.m.