Triple

T11973627
Position Surface form Disambiguated ID Type / Status
Subject Levice E284980 entity
Predicate hasTwinTown P919 FINISHED
Object Nowy Sącz, Poland E23790 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: Nowy Sącz, Poland | Statement: [Levice, hasTwinTown, Nowy Sącz, Poland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nowy Sącz, Poland
Context triple: [Levice, hasTwinTown, Nowy Sącz, Poland]
  • A. Nowy Sącz chosen
    Nowy Sącz is a historic city in southern Poland known for its well-preserved Old Town, cultural heritage, and role as a local economic and administrative center.
  • B. Kozienice, Poland
    Kozienice is a historic town in east-central Poland known for its location along the Vistula River and proximity to the Kozienice Landscape Park.
  • C. Stary Sącz
    Stary Sącz is a historic town in southern Poland known for its well-preserved medieval urban layout and cultural heritage.
  • D. Sianów
    Sianów is a small town in northwestern Poland known for its historical ties to the Pomerania region and its location near the Baltic coast.
  • E. Chojnice, Poland
    Chojnice is a historic town in northern Poland’s Pomeranian Voivodeship, known for its medieval architecture and role as a local cultural and economic 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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9039107e48190ae4c4efd6257dd3c completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4598d62a8819087f83912d1e45b27 completed May 1, 2026, 7:43 a.m.
Created at: April 8, 2026, 9:46 p.m.