Triple
T31399323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | واسی |
E800949
|
entity |
| Predicate | گروه_گویشوران |
P86353
|
FINISHED |
| Object | مردم نورستان |
—
|
NE NERFINISHED |
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: مردم نورستان | Statement: [واسی, گروه_گویشوران, مردم نورستان]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: گروه_گویشوران Context triple: [واسی, گروه_گویشوران, مردم نورستان]
-
A.
cultGroupOf
Indicates that one entity is a cult group to which the other entity belongs or is affiliated.
-
B.
vernacularGroup
chosen
Indicates a relationship where entities are grouped or associated based on sharing the same vernacular (local or commonly spoken) language.
-
C.
arealLinguisticGroup
Indicates a relationship where languages are grouped together based on shared features arising from geographic proximity and contact, rather than common genetic origin.
-
D.
linguisticSubgroup
Indicates that one linguistic group forms a subordinate or specialized subset within a larger linguistic group or family.
-
E.
SOIUSAGroup
Indicates a classification relationship where a mountain or geographic feature is assigned to a specific group according to the SOIUSA (International Standardized Mountain Subdivision of the Alps) system.
- F. None of above.
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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.