Triple
T15942789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapuri |
E386606
|
entity |
| Predicate | usesScriptVariantOf |
P51273
|
FINISHED |
| Object | Perso-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: Perso-Arabic script | Statement: [Shapuri, usesScriptVariantOf, Perso-Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptVariantOf Context triple: [Shapuri, usesScriptVariantOf, Perso-Arabic script]
-
A.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
-
B.
scriptVariantOf
chosen
Indicates that one script is a variant or alternative form of another script, typically differing in style, region, or historical development while remaining closely related.
-
C.
scriptVariantLanguage
Indicates that a language is a variant distinguished by its writing system or script from another, related language form.
-
D.
usedInScripts
Indicates that something (such as a tool, method, or resource) is employed or referenced within one or more scripts.
-
E.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.