Triple

T9714299
Position Surface form Disambiguated ID Type / Status
Subject Orya E235100 entity
Predicate writingSystemFor P454 FINISHED
Object Oriya 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: Oriya | Statement: [Orya, writingSystemFor, Oriya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oriya
Context triple: [Orya, writingSystemFor, Oriya]
  • A. Maithili
    Maithili is an Indo-Aryan language spoken primarily in the eastern Indian state of Bihar and neighboring regions, with a rich literary tradition and official recognition in India.
  • B. Bhojpuri
    Bhojpuri is an Indo-Aryan language spoken primarily in eastern Uttar Pradesh, western Bihar, and parts of Nepal, with a rich folk culture and a large diaspora community.
  • C. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • D. 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.
  • E. Santhali
    Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • 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_69ca84cd8fa0819090a5e243ceb37003 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9e0a1b548190b34c8571751ca1d3 completed April 1, 2026, 10:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69d19f900ca08190a52f042feab2afa3 completed April 4, 2026, 11:32 p.m.
Created at: March 30, 2026, 8:19 p.m.