Triple

T10489793
Position Surface form Disambiguated ID Type / Status
Subject Majang language E247384 entity
Predicate hasAlternativeName P39 FINISHED
Object Möjang E775664 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: Möjang | Statement: [Majang language, hasAlternativeName, Möjang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Möjang
Context triple: [Majang language, hasAlternativeName, Möjang]
  • A. Lamkang chosen
    Lamkang is a Tibeto-Burman language spoken by the Lamkang people, primarily in parts of Northeast India and Myanmar.
  • B. Mangdechhu
    Mangdechhu is a river in Bhutan known for flowing through ecologically rich protected areas and hosting major hydropower projects.
  • C. Suhungmung
    Suhungmung was a prominent 16th-century Ahom king of Assam known for major territorial expansion, administrative reforms, and successful resistance against external invasions.
  • D. Tingkhong
    Tingkhong is a notable town in the Indian state of Assam, recognized as one of the key urban centers within Dibrugarh district.
  • E. 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.
  • 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_69d381c309b88190af78aa681cf6a4c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d5097ca5c081908b47a08ca7885650 completed April 7, 2026, 1:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69d8dc9792308190b09d6aaed63dd418 completed April 10, 2026, 11:18 a.m.
Created at: April 6, 2026, 12:23 p.m.