Triple
T294024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urdu |
E6054
|
entity |
| Predicate | standardFormOf |
P2203
|
FINISHED |
| Object | Hindustani |
E31768
|
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: Hindustani | Statement: [Urdu, standardFormOf, Hindustani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hindustani Context triple: [Urdu, standardFormOf, Hindustani]
-
A.
Hindi
Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
-
B.
Bengali
Bengali is an Indo-Aryan language spoken primarily in the Bengal region of South Asia and serving as the official and most widely used language of Bangladesh and the Indian state of West Bengal.
-
C.
Sindhi
Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
-
D.
Gujarati
Gujarati is an Indo-Aryan language primarily spoken in the Indian state of Gujarat and by Gujarati communities worldwide.
-
E.
Khari Boli
chosen
Khari Boli is a major dialect of the Hindi-Urdu language continuum, historically associated with the Delhi region and serving as the primary basis for Standard Hindi.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e978420881908488df342a7d5e90 |
completed | Feb. 28, 2026, 1:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3a88778b48190856af2e89d21621a |
completed | March 1, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 1:06 p.m.