Triple

T12526720
Position Surface form Disambiguated ID Type / Status
Subject Beli Dvor E299457 entity
Predicate cityDistrict P2709 FINISHED
Object Savski venac E133514 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: Savski venac | Statement: [Beli Dvor, cityDistrict, Savski venac]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Savski venac
Context triple: [Beli Dvor, cityDistrict, Savski venac]
  • A. Šavnik
    Šavnik is a small mountainous town and municipality in northern Montenegro, known for its rugged landscape and proximity to the Durmitor region.
  • B. Savski Venac chosen
    Savski Venac is a central urban municipality of Belgrade, Serbia, known for its government institutions, major transport hubs, and historic neighborhoods.
  • C. Svratka
    Svratka is a river in the Czech Republic that flows through the city of Brno and is a significant watercourse in the South Moravian region.
  • D. Ravanica
    Ravanica is a river in central Serbia that flows through the region before joining the Velika Morava.
  • E. Ostružnica
    Ostružnica is a suburban neighborhood of Belgrade, Serbia, situated along the Sava River and known for its strategic transport links, including the Ostružnica Bridge.
  • 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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9545d7e6c819080c3a85c18caa1ae completed April 10, 2026, 7:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69f64bc393808190add527030a928517 completed May 2, 2026, 7:08 p.m.
Created at: April 8, 2026, 9:57 p.m.