Triple
T11342937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghan rupee |
E268644
|
entity |
| Predicate | exchangeStandard |
P35645
|
FINISHED |
| Object | silver standard |
—
|
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: silver standard | Statement: [Afghan rupee, exchangeStandard, silver standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeStandard Context triple: [Afghan rupee, exchangeStandard, silver standard]
-
A.
exchangeType
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
B.
exchangeAuthority
Indicates a relationship where control or decision-making power is transferred or swapped between entities.
-
C.
exchangeFormat
Indicates that one entity uses, supports, or is represented in a particular data or communication format for exchanging information with another system or entity.
-
D.
exchangeRegime
chosen
Indicates the type of currency exchange system or policy framework governing how a country’s currency is valued and traded relative to other currencies.
-
E.
exchangeContext
Indicates a relationship where two or more entities share or transfer contextual information or situational details between each other.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.