Triple
T617037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balochi |
E14427
|
entity |
| Predicate | influencedBy |
P9
|
FINISHED |
| Object | Sindhi |
E12831
|
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: Sindhi | Statement: [Balochi, influencedBy, Sindhi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sindhi Context triple: [Balochi, influencedBy, Sindhi]
-
A.
Sindhi
chosen
Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
-
B.
Saraiki
Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
-
C.
Dogri
Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
-
D.
Balochi
Balochi is an Iranian language spoken primarily by the Baloch people across Pakistan, Iran, and Afghanistan, with several dialects and a rich oral literary tradition.
-
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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e22f3688190a512bec3f0347814 |
completed | March 1, 2026, 8:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a56c4973c88190a7d234f480ecade5 |
completed | March 2, 2026, 10:54 a.m. |
Created at: March 1, 2026, 7:35 p.m.