Triple

T23505567
Position Surface form Disambiguated ID Type / Status
Subject Sampang language E572271 entity
Predicate hasSpeakersIn P16679 FINISHED
Object Bhojpur District, Nepal
Bhojpur District, Nepal is a hilly district in eastern Nepal known for its ethnolinguistic diversity and as a traditional center of Kirati culture.
E1595512 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: Bhojpur District, Nepal | Statement: [Sampang language, hasSpeakersIn, Bhojpur District, Nepal]
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: Bhojpur District, Nepal
Triple: [Sampang language, hasSpeakersIn, Bhojpur District, Nepal]
Generated description
Bhojpur District, Nepal is a hilly district in eastern Nepal known for its ethnolinguistic diversity and as a traditional center of Kirati culture.

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_69e245b5e4208190bac8a6509867e394 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a8ff97c88190a67f787e1674619e completed April 29, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f4551de388190b69dd42d9f7bde36 completed May 21, 2026, 5:48 p.m.
NEDg Description generation batch_6a0f4762e62c81908285cf6299f22250 completed May 21, 2026, 5:56 p.m.
NED2 Entity disambiguation (via description) batch_6a0f481aa71c8190bbbab462001d3586 completed May 21, 2026, 5:59 p.m.
Created at: April 17, 2026, 6:07 p.m.