Triple

T1163695
Position Surface form Disambiguated ID Type / Status
Subject Belgrade E24551 entity
Predicate locatedOnRiver P165 FINISHED
Object Sava E75220 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: Sava | Statement: [Belgrade, locatedOnRiver, Sava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sava
Context triple: [Belgrade, locatedOnRiver, Sava]
  • A. Sava chosen
    Sava is a major river in Central and Southeastern Europe that flows through countries including Slovenia, Croatia, Bosnia and Herzegovina, and Serbia before joining the Danube.
  • B. Istra River
    The Istra River is a waterway in the Moscow region of Russia that flows through the town of Istra before joining the Moskva River.
  • C. Neretva
    Neretva is a major river in the western Balkans, known for its emerald-green waters, deep canyons, and historic bridges such as the Stari Most in Mostar.
  • D. Drina
    The Drina is a significant river in the western Balkans, forming much of the border between Bosnia and Herzegovina and Serbia and known for its scenic canyons and historical importance.
  • E. Drava
    The Drava is a major Central European river that flows through countries including Italy, Austria, Slovenia, Croatia, and Hungary before joining the Danube.
  • 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_69a494060e148190abb42f971242c197 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcc9dc5081908e225a485186ab12 completed March 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad1c90c95081908af02d73f7d762ee completed March 8, 2026, 6:52 a.m.
Created at: March 1, 2026, 7:45 p.m.