Triple
T14810410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi riyal |
E348162
|
entity |
| Predicate | typicalBanknoteDenomination |
P12439
|
FINISHED |
| Object | 1 riyal |
—
|
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: 1 riyal | Statement: [Saudi riyal, typicalBanknoteDenomination, 1 riyal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBanknoteDenomination Context triple: [Saudi riyal, typicalBanknoteDenomination, 1 riyal]
-
A.
banknoteDenomination
Indicates the specific face value assigned to a banknote in a given currency.
-
B.
typeOfBanknotes
Indicates a relationship where one entity specifies the kind or category of banknotes associated with another entity.
-
C.
frequentlyUsedBanknotes
chosen
Indicates that the referenced banknotes are commonly or regularly used in transactions within a given context or system.
-
D.
denominationType
Indicates the specific category or kind of denomination associated with an entity, such as its type within a broader classification of denominations.
-
E.
currencyOfDenomination
Indicates that one currency unit is a specific denomination or face value within another currency system.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf35a5e081909321193ef37099d1 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:46 a.m.