Triple
T35593449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish |
E1028562
|
entity |
| Predicate | previousScriptType |
P17239
|
FINISHED |
| Object | Arabic-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: Arabic-based script | Statement: [Turkish, previousScriptType, Arabic-based script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousScriptType Context triple: [Turkish, previousScriptType, Arabic-based script]
-
A.
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).
-
B.
formerScript
chosen
Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
-
C.
previousPrimaryScriptingLanguage
Indicates that an entity was formerly the main or primary scripting language used by another entity before being replaced or superseded.
-
D.
previousServiceType
Indicates that one service type directly preceded another in a sequence or history of services.
-
E.
primaryScript
Indicates the writing system or script that is chiefly used to represent the language or content of an 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:05 p.m.