Triple

T7362770
Position Surface form Disambiguated ID Type / Status
Subject Kodava E169791 entity
Predicate alternateName P39 FINISHED
Object Kodava takk E169791 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: Kodava takk | Statement: [Kodava, alternateName, Kodava takk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kodava takk
Context triple: [Kodava, alternateName, Kodava takk]
  • A. Kodava chosen
    Kodava is a Dravidian language spoken primarily by the Kodava (Coorg) community in the Kodagu district of Karnataka, India.
  • B. Takaro
    Takaro is a residential suburb located within the city of Palmerston North in New Zealand.
  • C. Kuttantavar
    Kuttantavar is a regional name for Iravan, a minor but significant figure in the Mahabharata epic who is venerated in specific South Indian folk and temple traditions.
  • D. Tigak
    Tigak is an Austronesian language of the Meso-Melanesian subgroup spoken primarily in parts of Papua New Guinea.
  • E. Kopaida
    Kopaida is the Greek name for Lake Copais, a former large karstic lake in Boeotia, central Greece, that was historically significant for its drainage and agricultural reclamation.
  • 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_69c68a5ade988190885b7175f63b7534 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f15f218081909b5cc7a8cc695055 completed March 27, 2026, 9:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7fab3a9d88190b9193dd0729eba5a completed March 28, 2026, 3:58 p.m.
Created at: March 27, 2026, 3:06 p.m.