Triple
T12891742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hajipur |
E308384
|
entity |
| Predicate | localLanguage |
P1252
|
FINISHED |
| Object | Magahi |
E53011
|
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: Magahi | Statement: [Hajipur, localLanguage, Magahi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Magahi Context triple: [Hajipur, localLanguage, Magahi]
-
A.
Magahi
chosen
Magahi is an Eastern Indo-Aryan language spoken primarily in the Indian state of Bihar and surrounding regions.
-
B.
Mohanchoti
Mohanchoti is an island located within Lake Pichola in Udaipur, Rajasthan, India.
-
C.
Majangir
Majangir is an ethnic group of southwestern Ethiopia known for speaking the Majang language, part of the Surmic branch of the Nilo-Saharan language family.
-
D.
Maihar
Maihar is a town in Madhya Pradesh, India, renowned for its revered Maa Sharda Devi temple and its rich Hindustani classical music heritage.
-
E.
Majiwada
Majiwada is a prominent residential and commercial locality in Thane, Maharashtra, known for its major road junctions, high-rise complexes, and proximity to key urban amenities.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97146d2208190be5ae26e51193b67 |
completed | April 10, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a55be3288190b2bc0bd197431db3 |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:39 p.m.