Triple
T719731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baghdad |
E14388
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Iraqi dinar |
E37766
|
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: Iraqi dinar | Statement: [Baghdad, currency, Iraqi dinar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iraqi dinar Context triple: [Baghdad, currency, Iraqi dinar]
-
A.
Iraqi dinar
chosen
The Iraqi dinar is the official fiat currency of Iraq, issued by the Central Bank of Iraq and subdivided into 1,000 fils.
-
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.
Tunisian dinar
The Tunisian dinar is the official monetary unit of Tunisia, subdivided into 1,000 millimes and used for all domestic financial transactions.
-
D.
Jordanian dinar
The Jordanian dinar is the official currency of Jordan and one of the region’s more stable and widely used Middle Eastern currencies.
-
E.
Dirham
The dirham is a historical silver coin and monetary unit widely used in the Islamic world, originating as a standard currency under early Muslim caliphates.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58e65e8819098cba7e6a20d8f33 |
completed | March 1, 2026, 8:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a654de91bc819088d495c8a9cb4133 |
completed | March 3, 2026, 3:26 a.m. |
Created at: March 1, 2026, 7:37 p.m.