Triple

T15603971
Position Surface form Disambiguated ID Type / Status
Subject Asaf Jah III E375106 entity
Predicate languageUsed P238 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: [Asaf Jah III, languageUsed, Telugu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Telugu
Context triple: [Asaf Jah III, languageUsed, 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_69d85cce25008190b13b52745fbd719b completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e7d9328819090e93d55881269a5 completed April 16, 2026, 2:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff56d1607c8190a42dc664abe45b32 completed May 9, 2026, 3:46 p.m.
Created at: April 10, 2026, 4:12 a.m.