Triple

T1822771
Position Surface form Disambiguated ID Type / Status
Subject Imphal International Airport E40576 entity
Predicate locatedIn P40 FINISHED
Object Imphal E165058 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: Imphal | Statement: [Imphal International Airport, locatedIn, Imphal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Imphal
Context triple: [Imphal International Airport, locatedIn, Imphal]
  • A. Imphal chosen
    Imphal is the capital city of the Indian state of Manipur, known for its scenic valleys, historic Kangla Fort, and cultural significance in Northeast India.
  • B. Shillong
    Shillong is the capital city of the northeastern Indian state of Meghalaya, known for its scenic hills, colonial-era architecture, and vibrant cultural life.
  • C. Guwahati
    Guwahati is a major city in northeastern India, serving as a key cultural, economic, and transportation hub for the region.
  • D. Aizawl
    Aizawl is the hilly capital city of the Indian state of Mizoram, known for its scenic landscapes and vibrant Mizo culture in Northeast India.
  • E. Agartala
    Agartala is the capital city of the Indian state of Tripura and a major urban and economic center in Northeast India.
  • 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_69a8864526c081908a3a4d74f689e2c5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa662d13e88190a22b0faf0d848c7d completed March 6, 2026, 5:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae651f8f38819089fb40e7bb3dc2cb completed March 9, 2026, 6:13 a.m.
Created at: March 4, 2026, 7:32 p.m.