Triple
T18062307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BVMT |
E432203
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Tunisian dinar |
—
|
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: Tunisian dinar | Statement: [BVMT, currency, Tunisian dinar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tunisian dinar Context triple: [BVMT, currency, Tunisian dinar]
-
A.
Tunisian dinar
chosen
The Tunisian dinar is the official monetary unit of Tunisia, subdivided into 1,000 millimes and used for all domestic financial transactions.
-
B.
Tunisian riyal
The Tunisian riyal was a historical currency used in Tunisia during the Muradid dynasty period in the early modern era.
-
C.
Algerian dinar
The Algerian dinar is the official monetary unit of Algeria, issued and regulated by the Bank of Algeria.
-
D.
Tunisian franc
The Tunisian franc was the former national currency of Tunisia used before the adoption of the Tunisian dinar.
-
E.
Libyan dinar
The Libyan dinar is the official monetary unit of Libya, used for everyday transactions and economic activities throughout the country.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c107351c8190a2bfdb46754c2c6e |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 10:26 a.m.