Triple

T13365429
Position Surface form Disambiguated ID Type / Status
Subject Devgad E318925 entity
Predicate languageSpoken P151 FINISHED
Object Konkani E37892 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: Konkani | Statement: [Devgad, languageSpoken, Konkani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Konkani
Context triple: [Devgad, languageSpoken, 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 (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_69d806b7bbac8190b85278c87fa7aff3 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69da628c71ac81908cfa36342077766e completed April 11, 2026, 3:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7267e9d608190b36f58a92d4a9964 completed May 3, 2026, 10:42 a.m.
Created at: April 9, 2026, 9:32 p.m.