Triple

T1451472
Position Surface form Disambiguated ID Type / Status
Subject Sofia E31299 entity
Predicate hasRiver P165 FINISHED
Object Iskar River E180178 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: Iskar River | Statement: [Sofia, hasRiver, Iskar River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iskar River
Context triple: [Sofia, hasRiver, Iskar River]
  • A. Iskar River chosen
    The Iskar River is a significant river in Bulgaria that flows south through Sofia before turning north to cut a dramatic gorge through the Balkan Mountains on its way to the Danube.
  • B. 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.
  • C. Maritsa
    Maritsa is a significant river in the Balkans that flows through Bulgaria, Greece, and Turkey before emptying into the Aegean Sea.
  • D. 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.
  • E. Sava
    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.
  • 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_69a499171a28819085b993a3ac78e363 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c57bc0908190a57e6bc3d20d5e3c completed March 1, 2026, 11:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad51a1bf60819084e6be9587fe6eab completed March 8, 2026, 10:38 a.m.
Created at: March 1, 2026, 8 p.m.