Triple

T5362316
Position Surface form Disambiguated ID Type / Status
Subject Porbandar E103049 entity
Predicate hasOfficialLanguage P236 FINISHED
Object Hindi E5054 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: Hindi | Statement: [Porbandar, hasOfficialLanguage, Hindi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hindi
Context triple: [Porbandar, hasOfficialLanguage, Hindi]
  • A. Hindi chosen
    Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
  • B. Gujarati
    Gujarati is an Indo-Aryan language primarily spoken in the Indian state of Gujarat and by Gujarati communities worldwide.
  • C. 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.
  • D. Hindustani language
    The Hindustani language is a major Indo-Aryan language of South Asia that encompasses the closely related standardized forms of Hindi and Urdu and serves as a key lingua franca across northern India and Pakistan.
  • 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_69bd43daa3e4819090b59d127db70e57 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd865a0bb081909579cfe7c7974075 completed March 20, 2026, 5:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf21dbc540819086aca16af1aa6213 completed March 21, 2026, 10:55 p.m.
Created at: March 20, 2026, 2:02 p.m.