Triple
T15004495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | administration of Akbar |
E377673
|
entity |
| Predicate | standardCoin |
P78439
|
FINISHED |
| Object | rupiya |
—
|
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: rupiya | Statement: [administration of Akbar, standardCoin, rupiya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardCoin Context triple: [administration of Akbar, standardCoin, rupiya]
-
A.
coinedDenomination
Indicates that an entity created or introduced a particular name, term, or denomination for something.
-
B.
formerCoinDenomination
Indicates that one entity was previously used as a unit of coinage or monetary denomination in the context of the other entity, but is no longer in current use.
-
C.
coinageType
chosen
Indicates the specific type or category of coinage associated with an entity, such as its denomination, series, or monetary classification.
-
D.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
E.
mediumOfCoinage
Indicates the material or substance used as the physical medium in which a coin or form of money is produced.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7322b5c81909089cbbf816e1436 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.