Triple

T7844779
Position Surface form Disambiguated ID Type / Status
Subject Pingali Surana E181895 entity
Predicate workLanguage P15 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: [Pingali Surana, workLanguage, Telugu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Telugu
Context triple: [Pingali Surana, workLanguage, 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_69ca8285d6488190a95d4c02d7354b53 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb163d92fc8190a4efcb08d6b3d404 completed March 31, 2026, 12:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbdef32d4c8190a2e5c76d2db6c45f completed March 31, 2026, 2:49 p.m.
Created at: March 30, 2026, 4:48 p.m.