Triple

T3771021
Position Surface form Disambiguated ID Type / Status
Subject Shan Hills E83195 entity
Predicate contains P35 FINISHED
Object Hsipaw E368681 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: Hsipaw | Statement: [Shan Hills, contains, Hsipaw]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hsipaw
Context triple: [Shan Hills, contains, Hsipaw]
  • A. Parwanoo
    Parwanoo is an industrial town in the Solan district of Himachal Pradesh, India, known for its manufacturing units and proximity to the Haryana border.
  • B. Mongpan chosen
    Mongpan is a historic Shan principality in what is now Myanmar, known as one of the traditional Shan States.
  • C. Pasighat
    Pasighat is one of the oldest and most prominent towns in northeastern India, located in the East Siang district of Arunachal Pradesh and known as a gateway to the region’s tribal cultures and natural landscapes.
  • D. Salyan
    Salyan is a town in Azerbaijan known for its location in the Kura River lowlands and its role as a regional administrative and economic center.
  • E. Kangar
    Kangar is the main administrative and commercial center of the Malaysian state of Perlis.
  • 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_69ad8b235e608190b5a2b1d1bfcef50b completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcc307cf8819090730b5e697bb197 completed March 8, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4e5287908819084319b8dfa407635 completed March 14, 2026, 4:33 a.m.
Created at: March 8, 2026, 3:36 p.m.