Triple

T4892142
Position Surface form Disambiguated ID Type / Status
Subject PKP Intercity E109587 entity
Predicate servesStation P839 FINISHED
Object Toruń Główny E44061 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: Toruń Główny | Statement: [PKP Intercity, servesStation, Toruń Główny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Toruń Główny
Context triple: [PKP Intercity, servesStation, Toruń Główny]
  • A. Toruń chosen
    Toruń is a historic city in northern Poland, renowned for its well-preserved medieval Old Town and as the birthplace of astronomer Nicolaus Copernicus.
  • B. Bydgoszcz
    Bydgoszcz is a major city in northern Poland known as an important economic, cultural, and academic center on the Brda and Vistula rivers.
  • C. Ostrów Wielkopolski
    Ostrów Wielkopolski is a town in west-central Poland known for its industrial heritage and role as a local economic and cultural center in the Greater Poland region.
  • D. Augustów
    Augustów is a town in northeastern Poland known for its lakes, forests, and popular water tourism, including the historic Augustów Canal.
  • E. Olsztyn
    Olsztyn is a historic city in northern Poland known for its medieval architecture, lakes, and role as the capital of the Warmian-Masurian Voivodeship.
  • 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_69bd4410bbf88190aad50d2451c863d6 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e2444dc819088d5562e90d16d9b completed March 20, 2026, 3:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef7e68058819089e179a29ab700bc completed March 21, 2026, 7:56 p.m.
Created at: March 20, 2026, 1:28 p.m.