Triple

T21113804
Position Surface form Disambiguated ID Type / Status
Subject Melghat Tiger Reserve E520238 entity
Predicate languageOfLocalCommunities P5562 FINISHED
Object Korku NE NERFINISHED

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: Korku | Statement: [Melghat Tiger Reserve, languageOfLocalCommunities, Korku]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korku
Context triple: [Melghat Tiger Reserve, languageOfLocalCommunities, Korku]
  • A. Korku chosen
    Korku is an indigenous tribal language of central India, primarily spoken by the Korku people in parts of Maharashtra and neighboring states.
  • B. Horki
    Horki is a town in eastern Belarus known for its agricultural academy and regional administrative significance.
  • C. Osokorky
    Osokorky is a metro station on the Kyiv Metro system in Ukraine, serving the residential district of the same name on the city's left bank.
  • D. Kökeqota
    Kökeqota is a historic city in what is now Hohhot, Inner Mongolia, that served as the principal political and administrative center of the Northern Yuan dynasty after the fall of the Yuan in China.
  • E. Kurevere
    Kurevere is a small village located in Kiili Parish in northern Estonia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b509a318819092fbbcb21d1fe603 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72104e49c8190b75c2e14f6036e39 completed April 21, 2026, 7:02 a.m.
Created at: April 16, 2026, 2:54 p.m.