Triple

T11122306
Position Surface form Disambiguated ID Type / Status
Subject Manjeshwar E263044 entity
Predicate commonlySpokenLanguage P7445 FINISHED
Object Tulu E86782 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: Tulu | Statement: [Manjeshwar, commonlySpokenLanguage, Tulu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tulu
Context triple: [Manjeshwar, commonlySpokenLanguage, Tulu]
  • A. Tulu chosen
    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.
  • B. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • C. Ganjami
    Ganjami is a regional dialect of the Odia language spoken primarily in the Ganjam region of Odisha, India.
  • 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. 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_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79afa0ab88190ab6d61df8cf485ec completed April 9, 2026, 12:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69e42d8643748190a7801fc401dd2b5a completed April 19, 2026, 1:19 a.m.
Created at: April 8, 2026, 9:28 p.m.