Triple

T7620327
Position Surface form Disambiguated ID Type / Status
Subject Trzy Korony summit E172474 entity
Predicate accessFrom P1985 FINISHED
Object Szczawnica E304194 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: Szczawnica | Statement: [Trzy Korony summit, accessFrom, Szczawnica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Szczawnica
Context triple: [Trzy Korony summit, accessFrom, Szczawnica]
  • A. Szczawnica chosen
    Szczawnica is a Polish spa and tourist town in southern Lesser Poland, known for its mineral springs, health resorts, and scenic location in the Pieniny region near the Dunajec River.
  • B. Pszczyna
    Pszczyna is a historic town in southern Poland known for its well-preserved castle complex and picturesque old town.
  • C. Szczucin
    Szczucin is a small town in southern Poland, situated near the Vistula River and known historically as a local trade and transport hub.
  • D. Szczecinek
    Szczecinek is a town in northwestern Poland known for its lakeside setting, historic architecture, and role as a local economic and cultural center in the West Pomeranian Voivodeship.
  • E. Łęczna
    Łęczna is a town in eastern Poland known for its location near the Lublin Coal Basin and as a local administrative and service center.
  • 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_69c699506b308190826894dab1d9ea86 completed March 27, 2026, 2:50 p.m.
NER Named-entity recognition batch_69c6fa6148a88190be5150313fe23e7b completed March 27, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69d94aceb7108190beeec78587c04161 completed April 10, 2026, 7:09 p.m.
Created at: March 27, 2026, 3:55 p.m.