Triple
T10612246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughal Emperor |
E276032
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | mohur |
E403498
|
NE 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: mohur | Statement: [Mughal Emperor, currency, mohur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: mohur Context triple: [Mughal Emperor, currency, mohur]
-
A.
Sikh gold mohur
chosen
The Sikh gold mohur was a high-value gold coin issued by the Sikh Empire, notable for its rich numismatic and historical significance in 19th-century Punjab.
-
B.
Dholpur rupee
The Dholpur rupee was the historical monetary unit used in the princely state of Dholpur in pre-independence India.
-
C.
Bikaner rupee
The Bikaner rupee was the historical monetary unit used in the princely state of Bikaner in pre-independence India.
-
D.
Mughal rupee
The Mughal rupee was a silver coin that served as the standard monetary unit of the Mughal Empire, widely used in trade and administration across the Indian subcontinent.
-
E.
Mohar (historical currency of Nepal)
The Mohar was a traditional silver-based currency used in Nepal before the adoption of the modern Nepalese rupee.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5baf94819097b14a73af058f35 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95ec61b388190adee9b3577567709 |
completed | April 10, 2026, 8:34 p.m. |
Created at: April 8, 2026, 7:33 p.m.