Triple

T6093702
Position Surface form Disambiguated ID Type / Status
Subject Varanasi district E135826 entity
Predicate hasRiver P165 FINISHED
Object Ganges E4044 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: Ganges | Statement: [Varanasi district, hasRiver, Ganges]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ganges
Context triple: [Varanasi district, hasRiver, Ganges]
  • A. Ganges chosen
    The Ganges is a major river in northern India that is considered sacred in Hinduism and supports hundreds of millions of people along its basin.
  • B. Ganga
    Ganga is a queen associated with the ancient Kuru dynasty in Indian epic tradition, often linked to the river goddess personified in the Mahabharata.
  • C. Mata Ganga
    Mata Ganga was the wife of the fifth Sikh Guru, Guru Arjan Dev, and the mother of Guru Hargobind, playing a respected role in early Sikh history.
  • D. Namami Gange
    Namami Gange is an Indian government flagship initiative aimed at cleaning, rejuvenating, and protecting the Ganges River and its ecosystem.
  • E. Jamuna River
    The Jamuna River is the main distributary channel of the Brahmaputra in Bangladesh, forming one of the country’s largest and most dynamic river systems.
  • 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_69c0087cd3c48190b459848c72d84eb1 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05a9516ec819093e94ee8d3244e1b completed March 22, 2026, 9:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69c70adafa888190be606aba83a50302 completed March 27, 2026, 10:55 p.m.
Created at: March 22, 2026, 4:12 p.m.