Triple
T21201065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Indo-Aryan languages |
E522454
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Gujarati |
—
|
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: Gujarati | Statement: [New Indo-Aryan languages, hasPart, Gujarati]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gujarati Context triple: [New Indo-Aryan languages, hasPart, Gujarati]
-
A.
Gujarati
chosen
Gujarati is an Indo-Aryan language primarily spoken in the Indian state of Gujarat and by Gujarati communities worldwide.
-
B.
Parsi Gujarati
Parsi Gujarati refers to members of the Zoroastrian Parsi community who are culturally and linguistically rooted in the Gujarati-speaking region of western India.
-
C.
Hindi
Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
-
D.
Gojri
Gojri is an Indo-Aryan language traditionally spoken by the Gujjar community across parts of northern India and Pakistan.
-
E.
Dakhni Hindustani
Dakhni Hindustani is a regional variety of Hindustani historically spoken in the Deccan region of South India, blending elements of Urdu, Hindi, and local Dravidian languages.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73430c5a08190aeb6a62eec0f43a3 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 3:18 p.m.