Triple
T5377618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazakh SSR |
E113000
|
entity |
| Predicate | usedScriptForKazakh |
P56657
|
FINISHED |
| Object | Arabic 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: Arabic script | Statement: [Kazakh SSR, usedScriptForKazakh, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedScriptForKazakh Context triple: [Kazakh SSR, usedScriptForKazakh, Arabic script]
-
A.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
-
B.
scriptUsedForLanguage
chosen
Indicates that a particular writing script is employed to write or represent a given language.
-
C.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
D.
formerScript
Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
-
E.
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).
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.