Triple
T7170332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khoms |
E167177
|
entity |
| Predicate | usesCurrency |
P188
|
FINISHED |
| Object | Libyan dinar |
E6453
|
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: Libyan dinar | Statement: [Khoms, usesCurrency, Libyan dinar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Libyan dinar Context triple: [Khoms, usesCurrency, Libyan dinar]
-
A.
Libyan dinar
chosen
The Libyan dinar is the official monetary unit of Libya, used for everyday transactions and economic activities throughout the country.
-
B.
Libyan pound
The Libyan pound was the former national currency of Libya used during the monarchy period before being replaced by the Libyan dinar.
-
C.
Algerian dinar
The Algerian dinar is the official monetary unit of Algeria, issued and regulated by the Bank of Algeria.
-
D.
Tunisian dinar
The Tunisian dinar is the official monetary unit of Tunisia, subdivided into 1,000 millimes and used for all domestic financial transactions.
-
E.
Sudanese dinar
The Sudanese dinar was the former currency of Sudan, used mainly in the 1990s and early 2000s before being replaced by a reintroduced Sudanese pound.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85d8f208190915f6f4c05988b63 |
completed | March 27, 2026, 8:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7b910c2688190b28573c5d58542d5 |
completed | March 28, 2026, 11:18 a.m. |
Created at: March 27, 2026, 2:48 p.m.