Triple

T26868052
Position Surface form Disambiguated ID Type / Status
Subject Dhankuta District E676530 entity
Predicate hasMunicipality P847 FINISHED
Object Dhankuta Municipality
Dhankuta Municipality is an urban administrative center in eastern Nepal that serves as the main town and former district headquarters of Dhankuta District.
E1755318 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: Dhankuta Municipality | Statement: [Dhankuta District, hasMunicipality, Dhankuta Municipality]
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: Dhankuta Municipality
Triple: [Dhankuta District, hasMunicipality, Dhankuta Municipality]
Generated description
Dhankuta Municipality is an urban administrative center in eastern Nepal that serves as the main town and former district headquarters of Dhankuta District.

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_69eee9ba94bc8190b44c5d4397d04ecd completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61e99f138819097659bf61b6b35c2 completed May 2, 2026, 3:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a123a9f77b48190b7b51e19de68e5b1 completed May 23, 2026, 11:39 p.m.
NEDg Description generation batch_6a123d39d80c8190b626a7982b6ae4c5 completed May 23, 2026, 11:50 p.m.
NED2 Entity disambiguation (via description) batch_6a123d96adb48190899129e3369e56f7 completed May 23, 2026, 11:51 p.m.
Created at: April 27, 2026, 5:30 a.m.