Triple

T4669812
Position Surface form Disambiguated ID Type / Status
Subject Tarnovo E102934 entity
Predicate locatedOnRiver P165 FINISHED
Object Yantra River E264055 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: Yantra River | Statement: [Tarnovo, locatedOnRiver, Yantra River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yantra River
Context triple: [Tarnovo, locatedOnRiver, Yantra River]
  • A. Yantra River chosen
    The Yantra River is a significant river in northern Bulgaria that flows through historic towns like Veliko Tarnovo before joining the Danube.
  • B. Narayani River
    The Narayani River is a major river in central Nepal that flows along the edge of Chitwan National Park and forms part of the Ganges river system.
  • C. Shivna River
    The Shivna River is a regional river in the Indian state of Madhya Pradesh that flows near the town of Mandsaur and supports its local agriculture and ecology.
  • D. Shipra River
    The Shipra River is a sacred river in central India, especially revered in the city of Ujjain where it is central to major Hindu religious festivals such as the Kumbh Mela.
  • E. Haldi River
    The Haldi River is a river in the Indian state of West Bengal that joins the Hooghly River and forms part of the lower Ganges river system.
  • 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_69bd43d9cba4819086c1ab1c2d9d2133 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd634ef5608190925663e988e3585b completed March 20, 2026, 3:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1351018b48190910c3dad6c0f9850 completed March 23, 2026, 12:41 p.m.
Created at: March 20, 2026, 1:15 p.m.