Triple

T7147439
Position Surface form Disambiguated ID Type / Status
Subject Bhubaneswar E166603 entity
Predicate officialLanguage P236 FINISHED
Object Odia E24420 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: Odia | Statement: [Bhubaneswar, officialLanguage, Odia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Odia
Context triple: [Bhubaneswar, officialLanguage, Odia]
  • A. Odia chosen
    Odia is an Indo-Aryan language spoken primarily in the Indian state of Odisha, known for its rich literary tradition and classical language status.
  • B. Bangalee
    Bangalee is the popular stage nickname of Nigerian singer, songwriter, and harmonica-playing entertainer D'banj, known for his energetic Afrobeats hits.
  • C. Bangala
    Bangala is a regional variety of the Bantu language Lingala, spoken primarily in parts of the Democratic Republic of the Congo and neighboring areas.
  • D. Gōṇḍī
    Gōṇḍī is a South-Central Dravidian language spoken primarily by the Gondi people in central India.
  • E. Sambalpuri
    Sambalpuri is an Indo-Aryan language variety spoken primarily in and around the Sambalpur region of western Odisha, India, known for its distinct phonology and rich folk cultural traditions.
  • 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_69c68886779c8190a8e3fbabffe68253 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e7d4f3388190941f03fd80b0c223 completed March 27, 2026, 8:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bf817e4c819098268479f3fb181f completed March 28, 2026, 11:46 a.m.
Created at: March 27, 2026, 2:46 p.m.