Triple

T20355290
Position Surface form Disambiguated ID Type / Status
Subject Ptuj Library E496628 entity
Predicate locatedIn P40 FINISHED
Object Ptuj 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: Ptuj | Statement: [Ptuj Library, locatedIn, Ptuj]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ptuj
Context triple: [Ptuj Library, locatedIn, Ptuj]
  • A. Ptuj chosen
    Ptuj is one of Slovenia’s oldest towns, renowned for its well-preserved medieval architecture and rich cultural heritage along the Drava River.
  • B. Podhajce
    Podhajce is a historic town in western Ukraine, formerly part of interwar Poland, known for its multicultural heritage and role as a regional center in Galicia.
  • C. Telč
    Telč is a historic Czech town renowned for its well-preserved Renaissance and Baroque square, which is listed as a UNESCO World Heritage Site.
  • D. Gložan
    Gložan is a village in the Vojvodina region of northern Serbia, known for its Slovak ethnic community and agricultural character.
  • E. Ozalj
    Ozalj is a historic town in central Croatia known for its medieval castle and picturesque setting near the confluence of the Kupa and Dobra rivers.
  • 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_69e0b4a3f7f48190b37f354574028ca6 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67853f10881908ecde94036804a8a completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:25 a.m.