Triple
T21484547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Bank for Economic Cooperation |
E530082
|
entity |
| Predicate | currencyNowUsed |
P115600
|
FINISHED |
| Object | euro |
—
|
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: euro | Statement: [International Bank for Economic Cooperation, currencyNowUsed, euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyNowUsed Context triple: [International Bank for Economic Cooperation, currencyNowUsed, euro]
-
A.
currencyUsedFor
chosen
Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
-
B.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
-
C.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
D.
currentDenominationSince
Indicates the point in time from which the current denomination or value of something has been in effect.
-
E.
currencyPractice
Indicates the customary or standard way a particular currency is used, represented, or managed in transactions or economic contexts.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea365a8481909635f614b23e751f |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:21 p.m.