Triple

T9174402
Position Surface form Disambiguated ID Type / Status
Subject Bomdila E220159 entity
Predicate ethnicGroup P194 FINISHED
Object Monpa E213191 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: Monpa | Statement: [Bomdila, ethnicGroup, Monpa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Monpa
Context triple: [Bomdila, ethnicGroup, Monpa]
  • A. Monpa chosen
    Monpa are an indigenous ethnic group of the eastern Himalayas, primarily inhabiting the Tawang and West Kameng regions, known for their Tibetan Buddhist culture, traditional crafts, and high-altitude agrarian lifestyle.
  • B. Mongpan
    Mongpan is a historic Shan principality in what is now Myanmar, known as one of the traditional Shan States.
  • C. Thadou
    Thadou is a Kuki-Chin language spoken primarily by the Thadou people in northeastern India and neighboring regions.
  • D. Mishmi
    Mishmi are an indigenous tribal community of the eastern Himalayas, primarily inhabiting the remote, mountainous regions of Arunachal Pradesh in Northeast India.
  • E. Mugling
    Mugling is a small but important transport junction town in central Nepal, serving as a key crossroads between major highways connecting Kathmandu, Pokhara, and the southern plains.
  • 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_69ca83e467108190abcae6a33b3d4dad completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccbfa2f9708190a955bf28a4f04004 completed April 1, 2026, 6:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69d054a36ef881908079558050c67e7c completed April 4, 2026, midnight
Created at: March 30, 2026, 7:23 p.m.