Triple
T8877421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dholpur State |
E211321
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object |
Dholpur rupee
The Dholpur rupee was the historical monetary unit used in the princely state of Dholpur in pre-independence India.
|
E764133
|
NE FINISHED |
How this triple was built (4 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: Dholpur rupee | Statement: [Dholpur State, currency, Dholpur rupee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dholpur rupee Context triple: [Dholpur State, currency, Dholpur rupee]
-
A.
Bikaner rupee
The Bikaner rupee was the historical monetary unit used in the princely state of Bikaner in pre-independence India.
-
B.
Gwalior rupee
The Gwalior rupee was the historical monetary unit used in the princely state of Gwalior in pre-independence India.
-
C.
Hyderabadi rupee
The Hyderabadi rupee was the historical monetary unit used in the princely state of Hyderabad before its integration into the Indian monetary system.
-
D.
Travancore rupee
The Travancore rupee was the historical monetary unit used in the princely state of Travancore in southern India before the adoption of the Indian rupee.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Dholpur rupee Triple: [Dholpur State, currency, Dholpur rupee]
Generated description
The Dholpur rupee was the historical monetary unit used in the princely state of Dholpur in pre-independence India.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Dholpur rupee Target entity description: The Dholpur rupee was the historical monetary unit used in the princely state of Dholpur in pre-independence India.
-
A.
Bikaner rupee
The Bikaner rupee was the historical monetary unit used in the princely state of Bikaner in pre-independence India.
-
B.
Gwalior rupee
The Gwalior rupee was the historical monetary unit used in the princely state of Gwalior in pre-independence India.
-
C.
Hyderabadi rupee
The Hyderabadi rupee was the historical monetary unit used in the princely state of Hyderabad before its integration into the Indian monetary system.
-
D.
Travancore rupee
The Travancore rupee was the historical monetary unit used in the princely state of Travancore in southern India before the adoption of the Indian rupee.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61496870819097c55c73aca62aac |
completed | April 1, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfabaf57b88190a71d5303767ab517 |
completed | April 3, 2026, 11:59 a.m. |
| NEDg | Description generation | batch_69cfac9c743c8190a26f753111f07281 |
completed | April 3, 2026, 12:03 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfad54cf5c81908558fd4c21f2f3b6 |
completed | April 3, 2026, 12:06 p.m. |
Created at: March 30, 2026, 6:52 p.m.