Triple

T56827
Position Surface form Disambiguated ID Type / Status
Subject India E1124 entity
Predicate recognizedLanguage P238 FINISHED
Object Punjabi E3585 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: Punjabi | Statement: [India, recognizedLanguage, Punjabi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Punjabi
Context triple: [India, recognizedLanguage, Punjabi]
  • A. Punjabi language chosen
    Punjabi language is an Indo-Aryan language widely spoken in the Punjab region of India and Pakistan and among large diaspora communities worldwide.
  • B. Hindi
    Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
  • C. Gujarati
    Gujarati is an Indo-Aryan language primarily spoken in the Indian state of Gujarat and by Gujarati communities worldwide.
  • D. Urdu language
    Urdu is a major South Asian language, written in a Perso-Arabic script and widely used in Pakistan and parts of India in literature, media, and everyday communication.
  • E. Bengali
    Bengali is an Indo-Aryan language spoken primarily in the Bengal region of South Asia and serving as the official and most widely used language of Bangladesh and the Indian state of West Bengal.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69a248adc5b48190aa8db9fb092fb28a completed Feb. 28, 2026, 1:45 a.m.
NER Named-entity recognition batch_69a24b07f4a881909e32115e84da02a3 completed Feb. 28, 2026, 1:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69a266e716048190a57f681fccb4fdeb completed Feb. 28, 2026, 3:54 a.m.
Created at: Feb. 28, 2026, 1:50 a.m.