Triple

T2136373
Position Surface form Disambiguated ID Type / Status
Subject Barak Valley E46662 entity
Predicate hasTransportHub P2413 FINISHED
Object Silchar Airport E34709 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 Airport | Statement: [Barak Valley, hasTransportHub, Silchar Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Silchar Airport
Context triple: [Barak Valley, hasTransportHub, Silchar Airport]
  • A. Silchar Airport chosen
    Silchar Airport is a domestic airport serving the city of Silchar and the Barak Valley region in the Indian state of Assam.
  • B. Jorhat Airport
    Jorhat Airport is a domestic airport in Assam, India, serving the city of Jorhat and surrounding regions with regional air connectivity.
  • C. Dibrugarh Airport
    Dibrugarh Airport is a domestic airport in the Indian state of Assam that serves the city of Dibrugarh and the surrounding Upper Assam region.
  • D. Tezpur Airport
    Tezpur Airport is a domestic airport in Tezpur, Assam, India, serving as a regional air transport hub for the surrounding area.
  • E. Bagdogra Airport
    Bagdogra Airport is a major international airport in northern West Bengal, India, serving as a key gateway to the Darjeeling, Sikkim, and eastern Himalayan regions.
  • 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_69a88a174ab48190a5db20c132e5dccf completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abbdc4ce8c81908d143d5451681e6a completed March 7, 2026, 5:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae51acc0f88190a580e29d887170ec completed March 9, 2026, 4:50 a.m.
Created at: March 4, 2026, 7:44 p.m.