Triple
T3248369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatari riyal |
E68116
|
entity |
| Predicate | writingSystemOnCurrency |
P454
|
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: [Qatari riyal, writingSystemOnCurrency, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemOnCurrency Context triple: [Qatari riyal, writingSystemOnCurrency, Arabic script]
-
A.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
B.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
C.
definedMonetarySystem
Indicates that an authority or entity has established and specified the rules, structure, and characteristics of a particular monetary system.
-
D.
languageOnBanknotes
Indicates the language that is printed or used on a country's banknotes.
-
E.
writingSystemStandardized
Indicates that a writing system has been formally codified and regulated according to an accepted standard or set of rules.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf3e9ed0819096ac238098ac403c |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.