Triple

T8975731
Position Surface form Disambiguated ID Type / Status
Subject Sátoraljaújhely E214382 entity
Predicate hasTwinTown P919 FINISHED
Object Jarosław E284545 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: Jarosław | Statement: [Sátoraljaújhely, hasTwinTown, Jarosław]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jarosław
Context triple: [Sátoraljaújhely, hasTwinTown, Jarosław]
  • A. Jarosław chosen
    Jarosław is a historic town in southeastern Poland known for its well-preserved Old Town and role as a former important trade center.
  • B. Jasło
    Jasło is a small town in southeastern Poland, known as part of the historical region of Galicia and for its cultural and educational traditions.
  • C. Hrubieszów
    Hrubieszów is a historic town in eastern Poland near the Ukrainian border, known for its multicultural heritage and location in the Lublin region.
  • D. Kalisz
    Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
  • E. 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.
  • 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_69ca839ea8b88190922c6a326ffcc0d3 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6784d1808190899c980f76084ff8 completed April 1, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc96aa46c81908b95a23fd2b4da57 completed April 3, 2026, 2:06 p.m.
Created at: March 30, 2026, 7:02 p.m.