Triple

T36646200
Position Surface form Disambiguated ID Type / Status
Subject Samundri E904723 entity
Predicate hasAdministrativeUnit P3892 FINISHED
Object Samundri Tehsil
Samundri Tehsil is an administrative subdivision in the Faisalabad District of Punjab, Pakistan, encompassing the town of Samundri and its surrounding rural areas.
E2191811 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: Samundri Tehsil | Statement: [Samundri, hasAdministrativeUnit, Samundri Tehsil]
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: Samundri Tehsil
Triple: [Samundri, hasAdministrativeUnit, Samundri Tehsil]
Generated description
Samundri Tehsil is an administrative subdivision in the Faisalabad District of Punjab, Pakistan, encompassing the town of Samundri and its surrounding rural areas.

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_69f76e6d3a3c81909db73eda9e0516bd completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c72e54d88190b76b22cd33566d01 completed May 3, 2026, 10:07 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a09769fe88190b121ad34d2f30c15 completed June 23, 2026, 4:20 a.m.
NEDg Description generation batch_6a3a0d69be588190a63014cf862229be completed June 23, 2026, 4:36 a.m.
NED2 Entity disambiguation (via description) batch_6a3a0e5b312c8190a05b3b1414c09245 completed June 23, 2026, 4:40 a.m.
Created at: May 3, 2026, 4:11 p.m.