Triple

T7490968
Position Surface form Disambiguated ID Type / Status
Subject Taplejung District E177002 entity
Predicate airportServes P4363 FINISHED
Object Phungling E669320 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: Phungling | Statement: [Taplejung District, airportServes, Phungling]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Phungling
Context triple: [Taplejung District, airportServes, Phungling]
  • A. Phungling chosen
    Phungling is a town in eastern Nepal that serves as the main urban and commercial center of Taplejung District in Province No. 1.
  • B. Sairang
    Sairang is a small town in the Indian state of Mizoram, known for its scenic riverside setting and role as a transport and trading hub near the state capital Aizawl.
  • C. Bhailsa
    Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
  • D. Kattang
    Kattang is an Aboriginal Australian language traditionally spoken by the Worimi people of New South Wales.
  • E. Gogra
    Gogra is an alternative name for Kauriala, a locality whose identity is primarily tied to this regional designation.
  • 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_69c69f2583808190bd1a4936c42a5815 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f55bdb3481908653b46eafba011d completed March 27, 2026, 9:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c84eefbcec8190bef282452aaf5515 completed March 28, 2026, 9:58 p.m.
Created at: March 27, 2026, 3:43 p.m.