Triple

T2840696
Position Surface form Disambiguated ID Type / Status
Subject Panaji E62458 entity
Predicate officialLanguage P236 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: [Panaji, officialLanguage, Konkani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Konkani
Context triple: [Panaji, officialLanguage, 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. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • C. 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.
  • D. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • E. Maharashtri Prakrit
    Maharashtri Prakrit is an ancient Middle Indo-Aryan language historically used in western and central India, especially in classical poetry and drama, and is a key ancestor of several modern Indo-Aryan languages.
  • 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_69ab4c3d16bc81908b3a1c98fbd287fe completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf15b7288190a03d1193cc0544a6 completed March 7, 2026, 8:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69afe8cf32d08190bda89a513082813f completed March 10, 2026, 9:47 a.m.
Created at: March 6, 2026, 10:01 p.m.