Triple

T17145749
Position Surface form Disambiguated ID Type / Status
Subject Bheemunipatnam E416086 entity
Predicate officialLanguage P236 FINISHED
Object Telugu E5056 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: Telugu | Statement: [Bheemunipatnam, officialLanguage, Telugu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Telugu
Context triple: [Bheemunipatnam, officialLanguage, Telugu]
  • A. Telugu chosen
    Telugu is a major Dravidian language predominantly spoken in the Indian states of Andhra Pradesh and Telangana, known for its rich literary tradition and classical status.
  • B. Rayalaseema Telugu
    Rayalaseema Telugu is a regional dialect of the Telugu language spoken primarily in the Rayalaseema region of Andhra Pradesh, characterized by distinct phonetic and lexical features.
  • C. Kannada
    Kannada is a major Dravidian language predominantly spoken in the Indian state of Karnataka and surrounding regions, with a rich literary tradition spanning over a millennium.
  • D. Andhratharhi
    Andhratharhi is a town located in the Madhubani district of the Indian state of Bihar.
  • E. Tamil
    Tamil is a classical Dravidian language spoken predominantly in the Indian state of Tamil Nadu and in parts of Sri Lanka, with a rich literary tradition spanning over two millennia.
  • 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_69d886d15af4819092f92f8a129763e6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f2da515481909d19e421382eb755 completed April 18, 2026, 9:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a014158ed8c8190adb3c03c8a114a59 completed May 11, 2026, 2:39 a.m.
Created at: April 10, 2026, 5:36 a.m.