Triple
T10933980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Askunu |
E258279
|
entity |
| Predicate | neighboringLanguage |
P16383
|
FINISHED |
| Object | Pashayi |
E289721
|
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: Pashayi | Statement: [Askunu, neighboringLanguage, Pashayi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pashayi Context triple: [Askunu, neighboringLanguage, Pashayi]
-
A.
Pashai
chosen
The Pashai are an indigenous ethnic group of eastern Afghanistan, known for their distinct Indo-Aryan language and traditional mountain-based agrarian lifestyle.
-
B.
Alishang Pashayi
Alishang Pashayi is a regional variety of the Pashayi language spoken by Pashayi communities in the Alishang area of eastern Afghanistan.
-
C.
Kordar Pashayi
Kordar Pashayi is a variety of the Pashayi languages spoken by Pashayi communities in eastern Afghanistan.
-
D.
Tagau Pashayi
Tagau Pashayi is a specific variety of the Pashayi languages spoken by Pashayi communities in eastern Afghanistan.
-
E.
Pakhto
Pakhto is an alternative name for Pashto, an Eastern Iranian language spoken primarily in Afghanistan and Pakistan.
- 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.