Triple

T617843
Position Surface form Disambiguated ID Type / Status
Subject Battle of Chandannagar E14444 entity
Predicate tookPlaceOn P3824 FINISHED
Object Hooghly River E31966 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: Hooghly River | Statement: [Battle of Chandannagar, tookPlaceOn, Hooghly River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hooghly River
Context triple: [Battle of Chandannagar, tookPlaceOn, Hooghly River]
  • A. Hooghly River chosen
    The Hooghly River is a major distributary of the Ganges in eastern India that flows past Kolkata and serves as a vital waterway for transport, trade, and industry in West Bengal.
  • B. 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.
  • C. Jamuna
    Jamuna is an alternative name for the Yamuna, one of the major sacred rivers of northern India that flows through cities such as Delhi and Agra.
  • D. Ghaghara
    Ghaghara is a major Himalayan river in northern India and Nepal that significantly contributes to the flow of the Ganges.
  • E. Namami Gange
    Namami Gange is an Indian government flagship initiative aimed at cleaning, rejuvenating, and protecting the Ganges River and its ecosystem.
  • 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_69a4934b17c881909ace8270e8ddd202 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49e2418c881908552d2c4a5006e97 completed March 1, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a57b53ea008190be1a797f8d1d6c60 completed March 2, 2026, 11:58 a.m.
Created at: March 1, 2026, 7:35 p.m.