Triple
T11342905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFN |
E268643
|
entity |
| Predicate | currencyName |
P7046
|
FINISHED |
| Object | Afghan afghani |
E54475
|
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: Afghan afghani | Statement: [AFN, currencyName, Afghan afghani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Afghan afghani Context triple: [AFN, currencyName, Afghan afghani]
-
A.
Afghan afghani
chosen
The Afghan afghani is the official fiat currency of Afghanistan, issued and regulated by the country's central bank.
-
B.
Afghan rupee
The Afghan rupee was the former currency of Afghanistan used before the introduction of the Afghan afghani.
-
C.
Aden rupee
The Aden rupee was the former currency of the British-controlled port of Aden, used before being succeeded by the Aden shilling.
-
D.
Pakistani rupee
The Pakistani rupee is the official national currency of Pakistan, issued and regulated by the State Bank of Pakistan.
-
E.
Tajikistani somoni
The Tajikistani somoni is the official national currency of Tajikistan, used for all forms of monetary transactions within the country.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea1e360c8190a02d1e2d1d6f4b5d |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58b7033448190b848ccd3712c0b0e |
completed | April 20, 2026, 2:12 a.m. |
Created at: April 8, 2026, 9:33 p.m.