Triple
T25484146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India Government Mint, Noida |
E638652
|
entity |
| Predicate | currencyRegionServed |
P18115
|
FINISHED |
| Object | Indian 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: Indian rupee | Statement: [India Government Mint, Noida, currencyRegionServed, Indian rupee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyRegionServed Context triple: [India Government Mint, Noida, currencyRegionServed, Indian rupee]
-
A.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
-
B.
destinationCountryServed
Indicates that a given entity (such as a service, route, or provider) serves or operates to a specified destination country.
-
C.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
D.
countryOrRegionUsed
Indicates that something is used within, or applies to, a specific country or geographic region.
-
E.
currencyArea
chosen
Indicates that one entity is the geographic or economic region in which the other entity’s currency is officially used or valid.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 2:32 p.m.