Triple
T33747492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salamas |
E864737
|
entity |
| Predicate | usesScriptForLocalLanguages |
P150428
|
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: [Salamas, usesScriptForLocalLanguages, Perso-Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptForLocalLanguages Context triple: [Salamas, usesScriptForLocalLanguages, Perso-Arabic script]
-
A.
usesScriptFor
chosen
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
B.
usesLocalLanguageVariant
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
C.
usedInSourceLanguageScript
Indicates that a particular script is employed for writing in a given source language.
-
D.
hasScriptOfOfficialLanguage
Indicates that one entity is the writing system (script) used for the official language of another entity.
-
E.
usesScriptingLanguage
Indicates that an entity employs a scripting language to perform its operations, configuration, or automation tasks.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:45 a.m.