Triple

T8967111
Position Surface form Disambiguated ID Type / Status
Subject Neisse Viaduct E214165 entity
Predicate connects P390 FINISHED
Object Zgorzelec E222843 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: Zgorzelec | Statement: [Neisse Viaduct, connects, Zgorzelec]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zgorzelec
Context triple: [Neisse Viaduct, connects, Zgorzelec]
  • A. Zgorzelec chosen
    Zgorzelec is a town in southwestern Poland on the Lusatian Neisse River, forming a twin city with Görlitz in Germany and serving as an important local cultural and transport hub.
  • B. Samborzec
    Samborzec is a village and the seat of a rural administrative district in southeastern Poland’s Sandomierz County.
  • C. Chełmek
    Chełmek is a small town in southern Poland known historically for its shoe industry and its location near Oświęcim (Auschwitz).
  • D. Huczwa
    Huczwa is a river in eastern Poland that flows through the Lublin region before joining the Western Bug.
  • E. Zagorje
    Zagorje is a picturesque hilly region in northern Croatia known for its rural landscapes, thermal spas, and historic villages.
  • 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_69ca839cd6008190a1546a701a56710c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc676389948190aa78fdf6a5ae74a5 completed April 1, 2026, 12:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfd0a753f8819084b952f20997c8d6 completed April 3, 2026, 2:37 p.m.
Created at: March 30, 2026, 7:01 p.m.