Triple

T2846555
Position Surface form Disambiguated ID Type / Status
Subject Ravi E62996 entity
Predicate hasTributary P415 FINISHED
Object Chandra River E115472 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: Chandra River | Statement: [Ravi, hasTributary, Chandra River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chandra River
Context triple: [Ravi, hasTributary, Chandra River]
  • A. Chandra River chosen
    The Chandra River is a glacially fed mountain river in the Lahaul region of Himachal Pradesh, India, that flows through high-altitude valleys before joining the Bhaga River to help form the Chenab.
  • B. Siva River
    The Siva River is a tributary waterway in Russia that feeds into the Kama River within the Volga basin.
  • C. Krishna River
    The Krishna River is one of the major rivers of southern India, flowing through Maharashtra, Karnataka, Telangana, and Andhra Pradesh before emptying into the Bay of Bengal.
  • D. Sarayu
    Sarayu is a significant river in northern India, traditionally associated with the ancient city of Ayodhya and revered in Hindu mythology.
  • E. Banganga River
    The Banganga River is a smaller river in northern India that flows through the Himalayan foothills and joins the Beas River as one of its tributaries.
  • 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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf3ebbac819090e2bf98ed9fbd02 completed March 7, 2026, 8:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69bf32e44ed88190a7a6d9ea9097d8e6 completed March 22, 2026, 12:08 a.m.
Created at: March 6, 2026, 10:02 p.m.