Triple

T13901330
Position Surface form Disambiguated ID Type / Status
Subject Hindustani language E334228 entity
Predicate alsoKnownAs P39 FINISHED
Object Hindavi 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: Hindavi | Statement: [Hindustani language, alsoKnownAs, Hindavi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hindavi
Context triple: [Hindustani language, alsoKnownAs, Hindavi]
  • A. Hindko
    Hindko is a group of Indo-Aryan dialects spoken primarily in northern Pakistan, especially in parts of Khyber Pakhtunkhwa and Azad Kashmir.
  • B. Hindi chosen
    Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
  • C. Sant Bhasha
    Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
  • D. Maithili
    Maithili is an Indo-Aryan language spoken primarily in the eastern Indian state of Bihar and neighboring regions, with a rich literary tradition and official recognition in India.
  • E. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de25d9c7a48190ad8fb0ca676f4f7b completed April 14, 2026, 11:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69fba1c0b6848190b67051e0ccbdb707 completed May 6, 2026, 8:17 p.m.
Created at: April 9, 2026, 10:15 p.m.