Triple
T2020015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinar |
E44082
|
entity |
| Predicate | circulatedAlongside |
P26137
|
FINISHED |
| Object | silver dirham |
—
|
LITERAL 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: silver dirham | Statement: [Dinar, circulatedAlongside, silver dirham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulatedAlongside Context triple: [Dinar, circulatedAlongside, silver dirham]
-
A.
circulatedAs
Indicates that something was distributed, shared, or passed around in the form or role specified by the related entity.
-
B.
appearsAlongside
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
C.
wasLegalTenderAlongside
chosen
Indicates that one form of money was officially recognized and accepted as legal tender at the same time as another form of money within a given jurisdiction or period.
-
D.
operatedAlongside
Indicates that two or more entities functioned or were active together in a coordinated or concurrent manner within the same context or system.
-
E.
introducedAlongWith
Indicates that one entity was introduced or presented at the same time as another entity, as part of a joint or concurrent introduction.
- F. None of above.
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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.