Triple
T9239890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | abbasi |
E222031
|
entity |
| Predicate | denominationClass |
P87727
|
FINISHED |
| Object | Persian silver coinage |
—
|
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: Persian silver coinage | Statement: [abbasi, denominationClass, Persian silver coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationClass Context triple: [abbasi, denominationClass, Persian silver coinage]
-
A.
denominationType
Indicates the specific category or kind of denomination associated with an entity, such as its type within a broader classification of denominations.
-
B.
denomination
Indicates the specific religious or organizational branch, sect, or subgroup with which an entity is affiliated.
-
C.
denominationName
Indicates the specific religious or organizational denomination to which an entity belongs or is associated.
-
D.
denominationCode
Indicates the specific monetary unit or value category assigned to a currency, security, or financial instrument.
-
E.
denominationContext
Indicates the contextual or situational framework within which a particular denomination, classification, or named unit is defined or interpreted.
- F. None of above. chosen
Provenance (4 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf0a1e49081909c188f1e1e87039b |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:30 p.m.