Triple
T25070554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPE350 |
E627894
|
entity |
| Predicate | hasCurrencyScope |
P117741
|
FINISHED |
| Object | multi-currency European equities |
—
|
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: multi-currency European equities | Statement: [SPE350, hasCurrencyScope, multi-currency European equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyScope Context triple: [SPE350, hasCurrencyScope, multi-currency European equities]
-
A.
currencyScope
chosen
Indicates the range or jurisdiction within which a particular currency is valid, applicable, or intended to be used.
-
B.
hasCurrencyProject
Indicates that an entity is associated with or involved in a specific currency-related project.
-
C.
hasSettlementCurrency
Indicates that a financial transaction, contract, or account is settled using a specified currency.
-
D.
isUniquePerCurrency
Indicates that the related item or value must be unique within the scope of each individual currency.
-
E.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 6:10 a.m.