Triple

T19881697
Position Surface form Disambiguated ID Type / Status
Subject Kobarid E477789 entity
Predicate locatedNear P294 FINISHED
Object Tolmin 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: Tolmin | Statement: [Kobarid, locatedNear, Tolmin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tolmin
Context triple: [Kobarid, locatedNear, Tolmin]
  • A. Tolmin chosen
    Tolmin is a small Slovenian town in the Julian Alps, known as a gateway to the Soča Valley and for its scenic gorges, rivers, and outdoor recreation.
  • B. Kamnik
    Kamnik is a historic town in northern Slovenia known for its medieval architecture, nearby Kamnik–Savinja Alps, and role as a regional cultural and tourist center.
  • C. Kobarid
    Kobarid is a historic town in western Slovenia, known for its World War I heritage sites and scenic Alpine surroundings.
  • 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. Rovinka
    Rovinka is a village and municipality in western Slovakia, situated near Bratislava in the Senec District.
  • 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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e658df3f5c81909b5b290de91b8d50 completed April 20, 2026, 4:48 p.m.
Created at: April 10, 2026, 1:52 p.m.