Triple
T7073572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aravalli district |
E164757
|
entity |
| Predicate | hasOfficialLanguage |
P236
|
FINISHED |
| Object | Gujarati |
E8599
|
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: Gujarati | Statement: [Aravalli district, hasOfficialLanguage, Gujarati]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gujarati Context triple: [Aravalli district, hasOfficialLanguage, Gujarati]
-
A.
Gujarati
chosen
Gujarati is an Indo-Aryan language primarily spoken in the Indian state of Gujarat and by Gujarati communities worldwide.
-
B.
Hindi
Hindi is an Indo-Aryan language widely spoken across northern and central India and used in government, education, media, and popular culture.
-
C.
Gojri
Gojri is an Indo-Aryan language traditionally spoken by the Gujjar community across parts of northern India and Pakistan.
-
D.
Sindhi
Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
-
E.
Sant Bhasha
Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4cb76548190bd98876f8ba925b7 |
completed | March 27, 2026, 8:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7945fdafc81909c265373627af4e8 |
completed | March 28, 2026, 8:42 a.m. |
Created at: March 27, 2026, 2:39 p.m.