Triple

T28301181
Position Surface form Disambiguated ID Type / Status
Subject Mukhtiyar E713712 entity
Predicate officeHolder P537 FINISHED
Object Ranajit Pande
Ranajit Pande was a prominent Nepalese military and political leader who served as Mukhtiyar (equivalent to prime minister) during the early 19th century in the Kingdom of Nepal.
E1837335 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: Ranajit Pande | Statement: [Mukhtiyar, officeHolder, Ranajit Pande]
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: Ranajit Pande
Triple: [Mukhtiyar, officeHolder, Ranajit Pande]
Generated description
Ranajit Pande was a prominent Nepalese military and political leader who served as Mukhtiyar (equivalent to prime minister) during the early 19th century in the Kingdom of Nepal.

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_69efb524ab688190a1ce7ee7c9520932 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f644b2eba4819093973b8eeb3ed63d completed May 2, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24bb7c00ac8190a85b81584f1889c6 completed June 7, 2026, 12:29 a.m.
NEDg Description generation batch_6a24bff1b4c08190a75bde811f817760 completed June 7, 2026, 12:48 a.m.
NED2 Entity disambiguation (via description) batch_6a24caecac048190a5ea1ce35c7eca81 completed June 7, 2026, 1:35 a.m.
Created at: April 27, 2026, 11:35 p.m.