Triple
T1405975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algerian dinar |
E31691
|
entity |
| Predicate | writtenForm |
P2203
|
FINISHED |
| Object | dinar algérien |
E31691
|
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: dinar algérien | Statement: [Algerian dinar, writtenForm, dinar algérien]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: dinar algérien Context triple: [Algerian dinar, writtenForm, dinar algérien]
-
A.
Algerian dinar
chosen
The Algerian dinar is the official monetary unit of Algeria, issued and regulated by the Bank of Algeria.
-
B.
Algerian new franc
The Algerian new franc was a short-lived transitional currency used in Algeria during the early post-colonial period before the full adoption of the Algerian dinar.
-
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.
Libyan dinar
The Libyan dinar is the official monetary unit of Libya, used for everyday transactions and economic activities throughout the country.
-
E.
Moroccan dirham
The Moroccan dirham is the official monetary unit of Morocco, used for everyday transactions and issued by the country's central bank.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad015839908190b7f9f6c79dcc0367 |
completed | March 8, 2026, 4:55 a.m. |
Created at: March 1, 2026, 7:59 p.m.