Triple

T17612554
Position Surface form Disambiguated ID Type / Status
Subject GSB E428997 entity
Predicate westernTerminus P388 FINISHED
Object Ustroń 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: Ustroń | Statement: [GSB, westernTerminus, Ustroń]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ustroń
Context triple: [GSB, westernTerminus, Ustroń]
  • A. Ustroń chosen
    Ustroń is a spa town in southern Poland’s Silesian Beskids, known for its health resorts, mountain tourism, and role as a gateway to popular hiking routes.
  • B. Ostrołęka
    Ostrołęka is a town in east-central Poland known for its historical role in the Napoleonic Wars and as a local industrial and administrative center.
  • C. Olsztynek
    Olsztynek is a small historic town in northern Poland known for its open-air ethnographic museum and location within the picturesque Warmian-Masurian lake district.
  • D. Świnoujście
    Świnoujście is a Polish port city and seaside resort on the Baltic Sea, known for its wide beaches, spa facilities, and strategic location at the mouth of the Świna River.
  • E. Suwałki
    Suwałki is a city in northeastern Poland known for its cold climate, proximity to the Lithuanian border, and location within the historical region of Podlasie.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46d2eaa348190a8226eef8c0d6e31 completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 5:51 a.m.