Triple
T16608325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahore Mint |
E403500
|
entity |
| Predicate | currencyProducedFor |
P89898
|
FINISHED |
| Object | Sikh Empire’s monetary system |
—
|
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: Sikh Empire’s monetary system | Statement: [Lahore Mint, currencyProducedFor, Sikh Empire’s monetary system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyProducedFor Context triple: [Lahore Mint, currencyProducedFor, Sikh Empire’s monetary system]
-
A.
currencyProduced
chosen
Indicates that an entity is responsible for creating, issuing, or generating a particular form of currency.
-
B.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
-
C.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36093901881909b85af47f75879a9 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.