Triple

T377414
Position Surface form Disambiguated ID Type / Status
Subject Brahmaputra E8601 entity
Predicate passesCity P10456 FINISHED
Object Dibrugarh E32155 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: Dibrugarh | Statement: [Brahmaputra, passesCity, Dibrugarh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dibrugarh
Context triple: [Brahmaputra, passesCity, Dibrugarh]
  • A. Dibrugarh chosen
    Dibrugarh is a prominent city in northeastern India known as a major commercial and industrial hub of Assam, especially for its tea industry and oil and natural gas sectors.
  • B. Tezpur
    Tezpur is a historic city in northeastern India known for its cultural heritage, archaeological sites, and scenic location on the banks of the Brahmaputra River.
  • C. Jorhat
    Jorhat is a prominent city in northeastern India known as a cultural and educational hub and a key center of the tea industry in Assam.
  • D. Silchar
    Silchar is a prominent city in the Barak Valley region of northeastern India, known as a commercial, educational, and transportation hub of southern Assam.
  • E. Guwahati
    Guwahati is a major city in northeastern India, serving as a key cultural, economic, and transportation hub for the region.
  • 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_69a2e7f47dd08190a4e294ccbbe46cd4 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ee2b0ec481908fac41a4e1d20468 completed Feb. 28, 2026, 1:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3fafca1dc8190ba8f1cdec0ba337d completed March 1, 2026, 8:38 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.