Triple
T14521637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatari dirham |
E340664
|
entity |
| Predicate | fractionOfMainUnit |
P32237
|
FINISHED |
| Object | 0.01 Qatari 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: 0.01 Qatari riyal | Statement: [Qatari dirham, fractionOfMainUnit, 0.01 Qatari riyal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fractionOfMainUnit Context triple: [Qatari dirham, fractionOfMainUnit, 0.01 Qatari riyal]
-
A.
fractionalUnitCode
Indicates the code that specifies the fractional unit or sub-division of a primary unit used in a measurement or quantity.
-
B.
unitFractionalName
Indicates that one entity is the name or label used to represent a fractional unit of another entity (such as a measurement or quantity).
-
C.
minorUnitsPerUnit
chosen
Indicates the number of smaller sub-units that collectively make up one whole unit in a given measurement or currency system.
-
D.
fractionalUnitSymbol
Indicates the symbolic notation used to represent the fractional unit associated with a given quantity or measurement.
-
E.
valueRelativeToMainUnit
Indicates how a value is expressed in relation to a primary or reference unit, such as a main measurement or base quantity.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a72cff08190878b4bed9b0b5eb5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.