Triple

T12547569
Position Surface form Disambiguated ID Type / Status
Subject Barun River E300011 entity
Predicate tributaryOf P415 FINISHED
Object Arun River E240516 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: Arun River | Statement: [Barun River, tributaryOf, Arun River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arun River
Context triple: [Barun River, tributaryOf, Arun River]
  • A. Arun River chosen
    The Arun River is a major transboundary river of Tibet, Nepal, and India that flows south through the Himalayas to join the Kosi River system.
  • B. Chir River
    The Chir River is a waterway in southwestern Russia that flows through the steppe region of the Don Basin, historically significant as a route and battleground area, especially during World War II.
  • C. Lendi River
    The Lendi River is a minor river in southern India that flows through Maharashtra and Telangana before joining the Manjira River.
  • D. Ajay River
    Ajay River is a significant river in eastern India that flows through the states of Bihar, Jharkhand, and West Bengal before joining the Bhagirathi-Hooghly river system.
  • E. Ayvasedapur River
    The Ayvasedapur River is a tributary watercourse in India that joins with other streams to form the Pur River.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95481ba28819099f7cd2de02e8837 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff01ce8f988190b503af0cd5f2a97e completed May 9, 2026, 9:43 a.m.
Created at: April 8, 2026, 9:58 p.m.