Triple

T27910550
Position Surface form Disambiguated ID Type / Status
Subject Upper Mustang E705913 entity
Predicate ethnicGroup P194 FINISHED
Object Lopa
The Lopa are an indigenous Tibetan-influenced ethnic community of Nepal’s remote Upper Mustang region, known for their distinct language, culture, and traditional trans-Himalayan trade heritage.
E1793336 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: Lopa | Statement: [Upper Mustang, ethnicGroup, Lopa]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lopa
Triple: [Upper Mustang, ethnicGroup, Lopa]
Generated description
The Lopa are an indigenous Tibetan-influenced ethnic community of Nepal’s remote Upper Mustang region, known for their distinct language, culture, and traditional trans-Himalayan trade heritage.

Provenance (5 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_69ef96b5aad08190be36a277c31e7004 completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63a262d4c8190ab1f8bf3a3a1c444 completed May 2, 2026, 5:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a13036e24588190b59dac93ed5cc3b4 completed May 24, 2026, 1:55 p.m.
NEDg Description generation batch_6a13043132c48190bdd9d04f96ea323d completed May 24, 2026, 1:59 p.m.
NED2 Entity disambiguation (via description) batch_6a1304d78a548190bd80e0614e4b0efd completed May 24, 2026, 2:01 p.m.
Created at: April 27, 2026, 6:49 p.m.