Triple

T12847302
Position Surface form Disambiguated ID Type / Status
Subject Mandla district E307213 entity
Predicate hasMajorRiver P165 FINISHED
Object Banjar River E94427 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: Banjar River | Statement: [Mandla district, hasMajorRiver, Banjar River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banjar River
Context triple: [Mandla district, hasMajorRiver, Banjar River]
  • A. Banjar River chosen
    The Banjar River is a significant tributary in central India that feeds into the Narmada River system.
  • B. Kalang River
    The Kalang River is a coastal river in New South Wales, Australia, that flows through the Bellingen region before meeting the Pacific Ocean near the town of Urunga.
  • C. Binwa River
    Binwa River is a Himalayan river in northern India that flows through Himachal Pradesh as a significant tributary contributing to the Beas River system.
  • D. Kuria River
    Kuria River is a local watercourse associated with the Narita area in Japan, contributing to its natural landscape and drainage system.
  • E. Jalangi River
    The Jalangi River is a significant distributary of the Ganges in the Indian state of West Bengal, known for its role in regional irrigation, ecology, and local transportation.
  • 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96ff49efc8190bd6bbac510cc4705 completed April 10, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff56ade75c8190b556c3b0ba692a96 completed May 9, 2026, 3:45 p.m.
Created at: April 9, 2026, 5:36 p.m.