Triple

T20739778
Position Surface form Disambiguated ID Type / Status
Subject awa E509806 entity
Predicate represents P129 FINISHED
Object Awadhi 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: Awadhi | Statement: [awa, represents, Awadhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Awadhi
Context triple: [awa, represents, Awadhi]
  • A. Awadhi chosen
    Awadhi is an Indo-Aryan language of northern India, traditionally spoken in parts of Uttar Pradesh and surrounding regions and known for its rich literary and folk traditions.
  • B. Dakhni
    Dakhni is a historical Indo-Aryan language variety that developed in the Deccan region of India, blending early Urdu/Hindavi with local languages and Persian-Arabic influences.
  • C. Bagheli
    Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
  • D. Mirpuri
    Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
  • E. Dakhni Hindustani
    Dakhni Hindustani is a regional variety of Hindustani historically spoken in the Deccan region of South India, blending elements of Urdu, Hindi, and local Dravidian languages.
  • 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_69e0b4c589c08190834fb5d86d0efa2b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c20d9d4c8190a2fd87f8a33c313d completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:32 p.m.