Triple

T4753991
Position Surface form Disambiguated ID Type / Status
Subject Ferozepur E105542 entity
Predicate regionalLanguage P237 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: [Ferozepur, regionalLanguage, Punjabi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Punjabi
Context triple: [Ferozepur, regionalLanguage, Punjabi]
  • A. Punjabi
    Punjabi refers to the ethnolinguistic group native to the Punjab region of South Asia, known for its distinct language, culture, and traditions shared across parts of India and Pakistan.
  • B. 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.
  • C. Sindhi
    Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
  • D. Dogri
    Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
  • E. Sant Bhasha
    Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
  • 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_69bd43f07fa48190954317d01600994a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64e72d1c81908eb60960751e52b1 completed March 20, 2026, 3:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a6600e481909c3fb1decf23d7d8 completed March 21, 2026, 6:27 a.m.
Created at: March 20, 2026, 1:20 p.m.