Triple
T22679335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saadian sultans |
E560435
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | gold 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: gold dinar | Statement: [Saadian sultans, currency, gold dinar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: gold dinar Context triple: [Saadian sultans, currency, gold dinar]
-
A.
gold daric
The gold daric was a high-purity Persian gold coin of the Achaemenid Empire, widely used across its territories as a major trade and payment currency.
-
B.
Dinar
chosen
The Dinar is a historic gold coin and monetary unit widely used across the Islamic world, originating as the standard currency of early Muslim empires.
-
C.
Dinar
Dinar is a town and district in Turkey known as a regional hub in Afyonkarahisar Province, situated near the sources of the Büyük Menderes River.
-
D.
GOLD
GOLD is the radio call sign historically used by the British royal yacht HMY Britannia.
-
E.
Gulden
The Gulden was a historical European gold-based coin and monetary unit used in various German states, including Hesse-Kassel, before the adoption of more modern currencies.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785e4e7481909f1ebd6d8dbd6585 |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 3:11 p.m.