Triple

T1615577
Position Surface form Disambiguated ID Type / Status
Subject Silchar Airport E34709 entity
Predicate locatedIn P40 FINISHED
Object Silchar E31972 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: Silchar | Statement: [Silchar Airport, locatedIn, Silchar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Silchar
Context triple: [Silchar Airport, locatedIn, Silchar]
  • A. Silchar chosen
    Silchar is a prominent city in the Barak Valley region of northeastern India, known as a commercial, educational, and transportation hub of southern Assam.
  • B. 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.
  • C. Dibrugarh
    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.
  • D. Tinsukia
    Tinsukia is a town in Assam, India, known as a commercial hub of the region and a gateway to nearby wildlife-rich areas such as Dibru-Saikhowa National Park.
  • E. 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.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9099049e0819099763ecb09fb4f57 completed March 5, 2026, 4:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69aeb3a390bc8190891ebd5d8a48d818 completed March 9, 2026, 11:48 a.m.
Created at: March 4, 2026, 7:28 p.m.