Triple
T31399330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | واسی |
E800949
|
entity |
| Predicate | سیستم_نوشتاری_رایج |
P171827
|
FINISHED |
| Object | عمدتاً شفاهی |
—
|
LITERAL 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: عمدتاً شفاهی | Statement: [واسی, سیستم_نوشتاری_رایج, عمدتاً شفاهی]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: سیستم_نوشتاری_رایج Context triple: [واسی, سیستم_نوشتاری_رایج, عمدتاً شفاهی]
-
A.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
isMostWidelyUsedWritingSystem
Indicates that the subject writing system is used by more people or in more contexts than any other writing system.
-
C.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
D.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
-
E.
writingSystemStandardized
Indicates that a writing system has been formally codified and regulated according to an accepted standard or set of rules.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 29, 2026, 9:19 p.m.