Triple

T7620242
Position Surface form Disambiguated ID Type / Status
Subject Sokolica peak E172472 entity
Predicate hasNameInLanguage P15 FINISHED
Object Sokolica E193897 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: Sokolica | Statement: [Sokolica peak, hasNameInLanguage, Sokolica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sokolica
Context triple: [Sokolica peak, hasNameInLanguage, Sokolica]
  • A. Sokolica chosen
    Sokolica is a famous limestone peak in Poland’s Pieniny Mountains, renowned for its dramatic cliffs above the Dunajec River and its iconic lone pine tree.
  • B. Rakovica
    Rakovica is a suburban municipality of Belgrade, Serbia, known for its mixed residential and industrial areas and proximity to forested landscapes.
  • C. Pećinci
    Pećinci is a municipality in the Srem District of the autonomous province of Vojvodina in northern Serbia, known for its agricultural economy and proximity to Belgrade.
  • D. Šavnik
    Šavnik is a small mountainous town and municipality in northern Montenegro, known for its rugged landscape and proximity to the Durmitor region.
  • E. Konjšica
    Konjšica is a small settlement in central Slovenia, notable as the place where renowned conductor Carlos Kleiber died.
  • 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_69c699506b308190826894dab1d9ea86 completed March 27, 2026, 2:50 p.m.
NER Named-entity recognition batch_69c6fa6148a88190be5150313fe23e7b completed March 27, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69c86874d5e48190a07c48f667fb8f6e completed March 28, 2026, 11:47 p.m.
Created at: March 27, 2026, 3:55 p.m.