Triple
T10794876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laghman Province |
E254677
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Pashai |
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: Pashai | Statement: [Laghman Province, hasLanguage, Pashai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pashai Context triple: [Laghman Province, hasLanguage, Pashai]
-
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.
Barshaini
Barshaini is a small Himalayan village in Himachal Pradesh, India, that serves as a popular base and trailhead for treks into the Parvati Valley and surrounding high-altitude landscapes.
-
C.
Kushva
Kushva is a small industrial city in Russia’s Sverdlovsk Oblast, historically known for its iron ore mining in the Ural Mountains.
-
D.
Khotta
Khotta is an alternate name for the Khortha language, an Indo-Aryan language spoken primarily in the Indian state of Jharkhand.
-
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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733321dd881909dcd4224dfa9822a |
completed | April 9, 2026, 5:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69deb0c85d288190b13b1bc66921332c |
completed | April 14, 2026, 9:25 p.m. |
Created at: April 8, 2026, 9:17 p.m.