Triple
T346678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pashto language |
E6957
|
entity |
| Predicate | usesScriptVariant |
P5922
|
FINISHED |
| Object | Naskh-based script |
—
|
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: Naskh-based script | Statement: [Pashto language, usesScriptVariant, Naskh-based script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptVariant Context triple: [Pashto language, usesScriptVariant, Naskh-based script]
-
A.
scriptVariantLanguage
chosen
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
-
B.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
C.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
D.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
E.
scriptOnFlag
Indicates that a script is attached to and/or executed when a specific flag or condition is set.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.