Triple

T7016929
Position Surface form Disambiguated ID Type / Status
Subject Kohima E162720 entity
Predicate locatedIn P40 FINISHED
Object Kohima district E162720 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: Kohima district | Statement: [Kohima, locatedIn, Kohima district]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kohima district
Context triple: [Kohima, locatedIn, Kohima district]
  • A. Kohima chosen
    Kohima is the hilly capital city of Nagaland, known for its strategic role in World War II and its rich Naga cultural heritage.
  • B. Tuensang
    Tuensang is a town in northeastern India that serves as an important administrative and cultural center in the state of Nagaland.
  • C. Tinsukia district
    Tinsukia district is an administrative region in the Indian state of Assam known for its rich biodiversity, tea gardens, and proximity to major wildlife reserves.
  • D. Jorhat district
    Jorhat district is an administrative district in the Indian state of Assam, known for its tea gardens, cultural heritage, and historical significance in Upper Assam.
  • E. Lakhimpur district
    Lakhimpur district is an administrative region in the Indian state of Assam, known for its fertile plains, agriculture, and location in the Brahmaputra Valley.
  • 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_69c6885a127c8190867b059bdccf13ff completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1d629fc81908854390ddf99b1db completed March 27, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_69c775656fe48190a9690f5aaca3ba4c completed March 28, 2026, 6:29 a.m.
Created at: March 27, 2026, 2:34 p.m.