Triple
T19420697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bawshar |
E485842
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Omani rial |
—
|
NE NERFINISHED |
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: Omani rial | Statement: [Bawshar, currency, Omani rial]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Omani rial Context triple: [Bawshar, currency, Omani rial]
-
A.
Omani rial
chosen
The Omani rial is the official currency of Oman, known for its high value relative to most other world currencies.
-
B.
Saudi riyal
The Saudi riyal is the official monetary unit of Saudi Arabia, used nationwide for all financial transactions and pegged to the US dollar.
-
C.
Dubai riyal
The Dubai riyal was a former currency used in Dubai and some neighboring Trucial States before being replaced by the United Arab Emirates dirham.
-
D.
Bahraini dinar
The Bahraini dinar is the official currency of Bahrain, known for having one of the highest exchange values in the world.
-
E.
Qatari dirham
The Qatari dirham is a fractional monetary unit used as a subunit of Qatar’s national currency.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63214d768819082129100d7116521 |
completed | April 20, 2026, 2:03 p.m. |
Created at: April 10, 2026, 1:37 p.m.