Triple
T18885588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Yemeni dinar |
E461947
|
entity |
| Predicate | replaced |
P101
|
FINISHED |
| Object | Adeni rupee |
—
|
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: Adeni rupee | Statement: [South Yemeni dinar, replaced, Adeni rupee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adeni rupee Context triple: [South Yemeni dinar, replaced, Adeni rupee]
-
A.
Aden rupee
chosen
The Aden rupee was the former currency of the British-controlled port of Aden, used before being succeeded by the Aden shilling.
-
B.
Baroda rupee
The Baroda rupee was the historical monetary unit used in the princely State of Baroda in pre-independence India.
-
C.
Bikaner rupee
The Bikaner rupee was the historical monetary unit used in the princely state of Bikaner in pre-independence India.
-
D.
Nanakshahi rupee
The Nanakshahi rupee was the historical monetary unit used by Sikh misls, notably during the 18th-century Sikh Confederacy in Punjab.
-
E.
Hyderabadi rupee
The Hyderabadi rupee was the historical monetary unit used in the princely state of Hyderabad before its integration into the Indian monetary system.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d53e608190b8740c092b6e1523 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 10, 2026, 11:57 a.m.