Triple

T13804107
Position Surface form Disambiguated ID Type / Status
Subject Western Tamil Nadu E331716 entity
Predicate hasHillStation P24292 FINISHED
Object Kotagiri E686202 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: Kotagiri | Statement: [Western Tamil Nadu, hasHillStation, Kotagiri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kotagiri
Context triple: [Western Tamil Nadu, hasHillStation, Kotagiri]
  • A. Kotagiri chosen
    Kotagiri is a hill station town in the Nilgiri district of Tamil Nadu, India, known for its cool climate, tea plantations, and scenic mountain landscapes.
  • B. Hattiangadi
    Hattiangadi is a village in the Kundapura region of Karnataka, India, known for its historic temples and coastal cultural heritage.
  • C. Kundagannada
    Kundagannada is a regional dialect of the Kannada language spoken primarily in the coastal districts of Karnataka, India.
  • D. Hogenakkal
    Hogenakkal is a small town in Tamil Nadu, India, known as the gateway to the famous Hogenakkal Falls on the Kaveri River.
  • E. Kukanoor
    Kukanoor is a historic village in Karnataka, India, known for its ancient temples and archaeological significance.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de026c36108190a7436034a730a261 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7b08bd7c48190bcdf110ccd27c003 completed May 3, 2026, 8:31 p.m.
Created at: April 9, 2026, 10:12 p.m.