Triple
T22078081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Pakistan |
E545573
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Pakistani rupee |
—
|
NE NERFINISHED |
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: Pakistani rupee | Statement: [West Pakistan, currency, Pakistani rupee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pakistani rupee Context triple: [West Pakistan, currency, Pakistani rupee]
-
A.
Pakistani rupee
chosen
The Pakistani rupee is the official national currency of Pakistan, issued and regulated by the State Bank of Pakistan.
-
B.
Afghan rupee
The Afghan rupee was the former currency of Afghanistan used before the introduction of the Afghan afghani.
-
C.
Indian rupee
The Indian rupee is the official monetary unit of India, issued and regulated by the Reserve Bank of India and widely used in the country’s domestic and international economic transactions.
-
D.
Aden rupee
The Aden rupee was the former currency of the British-controlled port of Aden, used before being succeeded by the Aden shilling.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b38844819084526372fa6c6e35 |
completed | April 28, 2026, 9:37 p.m. |
Created at: April 16, 2026, 8:28 p.m.