Triple

T21628202
Position Surface form Disambiguated ID Type / Status
Subject T. M. A. Pai E533757 entity
Predicate nativeLanguage P151 FINISHED
Object Konkani 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: Konkani | Statement: [T. M. A. Pai, nativeLanguage, Konkani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Konkani
Context triple: [T. M. A. Pai, nativeLanguage, Konkani]
  • A. Konkani chosen
    Konkani is an Indo-Aryan language spoken primarily along India’s Konkan coast, especially in Goa and parts of Karnataka and Maharashtra.
  • B. Marathi–Konkani languages
    Marathi–Konkani languages are a group of closely related Indo-Aryan languages and dialects spoken primarily along India’s western coastal region, especially in Maharashtra, Goa, and parts of Karnataka.
  • C. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • D. Tulu
    Tulu is a Dravidian language spoken primarily in the coastal regions of Karnataka and northern Kerala in southwestern India, known for its rich oral traditions and distinct cultural identity.
  • E. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • 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_69e0c464fba881908d0ff2ac80511ce1 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5214e72c8190af109089f58fca4f completed April 27, 2026, 12:09 p.m.
Created at: April 16, 2026, 6:34 p.m.