Triple

T19410063
Position Surface form Disambiguated ID Type / Status
Subject Boudh district E485563 entity
Predicate hasLanguage P15 FINISHED
Object Sambalpuri NE NERFINISHED

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: Sambalpuri | Statement: [Boudh district, hasLanguage, Sambalpuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sambalpuri
Context triple: [Boudh district, hasLanguage, Sambalpuri]
  • A. Sambalpuri chosen
    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.
  • B. Sambalpur
    Sambalpur is a historic city and former princely region in western Odisha, India, known for its cultural heritage, textile traditions, and role in 19th-century colonial-era political events.
  • C. Sambalpuri people
    The Sambalpuri people are an ethnocultural community from western Odisha, India, known for their distinct Sambalpuri language, folk traditions, and vibrant handwoven textiles.
  • D. Mangolpuri
    Mangolpuri is a densely populated residential and industrial neighborhood located in the North West part of Delhi, India.
  • E. Gōṇḍī
    Gōṇḍī is a South-Central Dravidian language spoken primarily by the Gondi people in central India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62af3eaa081909e9537a2c57dc6c1 completed April 20, 2026, 1:32 p.m.
Created at: April 10, 2026, 1:37 p.m.