Triple

T13467439
Position Surface form Disambiguated ID Type / Status
Subject Marathi–Konkani languages E311539 entity
Predicate hasMember P10 FINISHED
Object Koli 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: Koli Konkani | Statement: [Marathi–Konkani languages, hasMember, Koli Konkani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koli Konkani
Context triple: [Marathi–Konkani languages, hasMember, Koli 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. Kolami
    Kolami is a Dravidian language spoken primarily by the Kolam tribal communities in central India, especially in parts of Maharashtra and Telangana.
  • D. Ganjami
    Ganjami is a regional dialect of the Odia language spoken primarily in the Ganjam region of Odisha, India.
  • E. 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.
  • 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf101a1081909f2aba6da47baacc completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f74629f1408190b54194fe794be39a completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:42 p.m.