Triple
T6482055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BDF |
E146417
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | Bahraini dinar |
E92656
|
NE 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: Bahraini dinar | Statement: [BDF, uses, Bahraini dinar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bahraini dinar Context triple: [BDF, uses, Bahraini dinar]
-
A.
Bahraini dinar
chosen
The Bahraini dinar is the official currency of Bahrain, known for having one of the highest exchange values in the world.
-
B.
Kuwaiti dinar
The Kuwaiti dinar is the official currency of Kuwait and is known for having one of the highest exchange values in the world.
-
C.
Qatari dirham
The Qatari dirham is a fractional monetary unit used as a subunit of Qatar’s national currency.
-
D.
Qatari riyal
The Qatari riyal is the official national currency of Qatar, issued by the Qatar Central Bank and commonly used in all financial transactions throughout the country.
-
E.
Hejaz riyal
The Hejaz riyal was the historical monetary unit used in the early 20th century in the Kingdom of Hejaz, in the western Arabian Peninsula.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0090158c08190af0df9a2348d2d52 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a6b2e9881908b715573e7ba7458 |
completed | March 22, 2026, 10:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c653afb1148190a8683f24a553f64d |
completed | March 27, 2026, 9:53 a.m. |
Created at: March 22, 2026, 4:51 p.m.