Triple

T21108483
Position Surface form Disambiguated ID Type / Status
Subject Sassi Punnu E520113 entity
Predicate centralMaleCharacter P49704 FINISHED
Object Punnu NE NERFINISHED

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: Punnu | Statement: [Sassi Punnu, centralMaleCharacter, Punnu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Punnu
Context triple: [Sassi Punnu, centralMaleCharacter, Punnu]
  • A. Punhana
    Punhana is a prominent town in Haryana, India, known as one of the key urban centers of Nuh district.
  • B. Pouni
    Pouni is a town in the Reasi district of the Jammu and Kashmir region of India, serving as one of its local commercial and administrative centers.
  • C. Pooncarie
    Pooncarie is a small rural town in far south-west New South Wales, Australia, known for its remote outback setting and proximity to the Darling River.
  • D. Pujali
    Pujali is a small town and municipality in the Indian state of West Bengal, situated near Kolkata along the Hooghly River.
  • E. Punnun chosen
    Punnun is a legendary prince and tragic lover from the Sindhi and Balochi folktale "Sassi Punnun," renowned for his doomed romance with Sassi.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b509a318819092fbbcb21d1fe603 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e720ffa998819082db225363ac3b23 completed April 21, 2026, 7:02 a.m.
Created at: April 16, 2026, 2:54 p.m.