Triple

T22443465
Position Surface form Disambiguated ID Type / Status
Subject Bhagalpur region E554810 entity
Predicate language P15 FINISHED
Object Angika 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: Angika | Statement: [Bhagalpur region, language, Angika]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Angika
Context triple: [Bhagalpur region, language, Angika]
  • A. Angika chosen
    Angika is an Eastern Indo-Aryan language spoken primarily in parts of Bihar and neighboring regions of India.
  • B. Aruna
    Aruna is a feminine given name most notably borne by Indian independence activist and political leader Aruna Asaf Ali.
  • C. Aruna
    Aruna is a figure in Hindu mythology known as the personified dawn and the divine charioteer who drives the sun god Surya across the sky.
  • D. Arambala
    Arambala is a small municipality in northeastern El Salvador known for its rural setting and location within the mountainous Morazán region.
  • E. Nabaneeta
    Nabaneeta is a feminine given name most notably borne by the acclaimed Indian Bengali writer and academic Nabaneeta Dev Sen.
  • 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ae40f9081908674015beb33f74e completed April 29, 2026, 1:12 a.m.
Created at: April 16, 2026, 8:47 p.m.