Triple

T15557878
Position Surface form Disambiguated ID Type / Status
Subject Zelenci Springs E370917 entity
Predicate locatedNear P294 FINISHED
Object Kranjska Gora E95582 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: Kranjska Gora | Statement: [Zelenci Springs, locatedNear, Kranjska Gora]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kranjska Gora
Context triple: [Zelenci Springs, locatedNear, Kranjska Gora]
  • A. Kranjska Gora chosen
    Kranjska Gora is a well-known Slovenian alpine resort town famed for skiing, hiking, and World Cup winter sports events.
  • B. Bovec
    Bovec is a small Slovenian town known for its alpine scenery and outdoor adventure tourism, including hiking, skiing, and white-water sports.
  • C. Slovenj Gradec
    Slovenj Gradec is a historic town in northern Slovenia known for its cultural heritage and picturesque Alpine surroundings.
  • D. Brnik
    Brnik is a village in Slovenia best known as the site of the country’s main international gateway, Ljubljana Jože Pučnik Airport.
  • E. Portorož
    Portorož is a popular Slovenian seaside resort town on the Adriatic coast, known for its beaches, spa tourism, and vibrant holiday atmosphere.
  • 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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04dda3ab88190ab383333ce69fe8f completed April 16, 2026, 2:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff456427988190bddea01f5cb159d9 completed May 9, 2026, 2:32 p.m.
Created at: April 10, 2026, 4:09 a.m.