Triple

T17481519
Position Surface form Disambiguated ID Type / Status
Subject Szklarska Poręba E425670 entity
Predicate hasRoadConnectionTo P11435 FINISHED
Object Jakuszyce 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: Jakuszyce | Statement: [Szklarska Poręba, hasRoadConnectionTo, Jakuszyce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jakuszyce
Context triple: [Szklarska Poręba, hasRoadConnectionTo, Jakuszyce]
  • A. Jakuszyce chosen
    Jakuszyce is a Polish mountain village in the Jizera Mountains, known as a major cross-country skiing and biathlon center near the border with the Czech Republic.
  • B. Kaczyce
    Kaczyce is a village in southern Poland’s Silesian region, situated near the Czech border.
  • C. Juszczyn
    Juszczyn is a village in southern Poland located within the administrative district of Gmina Maków Podhalański in Lesser Poland Voivodeship.
  • D. Jachówka
    Jachówka is a village in southern Poland located within the administrative district of Gmina Budzów in Lesser Poland Voivodeship.
  • E. Rakowice
    Rakowice is a historic district in Kraków, Poland, known for its large military cemetery and proximity to the city center.
  • 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_69d889dccf7481909264a1844a2e9100 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451bfd75481908c20bc2c1cbff593 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:48 a.m.