Triple
T10934011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkunwari |
E258280
|
entity |
| Predicate | isMutuallyIntelligibleWith |
P7448
|
FINISHED |
| Object | Wasi-wari (Vasi-vari) |
E228808
|
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: Wasi-wari (Vasi-vari) | Statement: [Ashkunwari, isMutuallyIntelligibleWith, Wasi-wari (Vasi-vari)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wasi-wari (Vasi-vari) Context triple: [Ashkunwari, isMutuallyIntelligibleWith, Wasi-wari (Vasi-vari)]
-
A.
Wasi-wari
Wasi-wari, also known as Prasuni, is a lesser-known Indo-Aryan language spoken in parts of northern Pakistan.
-
B.
Vasi-weri
Vasi-weri is an alternative name for the Prasun language, an Indo-Iranian language spoken in parts of Afghanistan.
-
C.
Vasi-vari
chosen
Vasi-vari is an Indo-Iranian language spoken in parts of Afghanistan, more widely known as the Prasun language.
-
D.
Warji
Warji is a Chadic language spoken primarily in northern Nigeria by the Warji people.
-
E.
Varekai
Varekai is a Cirque du Soleil touring circus production known for its fantastical forest setting, acrobatic performances, and imaginative storytelling.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ae073881909720febe9f5f296a |
completed | April 9, 2026, 9:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2176328448190bbce6735ec97507a |
completed | April 17, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:23 p.m.