Triple
T18327719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decimal Currency Board |
E439055
|
entity |
| Predicate | hasCurrencyAfter |
P89148
|
FINISHED |
| Object | pound sterling (decimal) |
—
|
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: pound sterling (decimal) | Statement: [Decimal Currency Board, hasCurrencyAfter, pound sterling (decimal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyAfter Context triple: [Decimal Currency Board, hasCurrencyAfter, pound sterling (decimal)]
-
A.
successorCurrencyOf
chosen
Indicates that one currency has replaced another as the official or primary currency in use.
-
B.
successorCurrenciesUsed
Indicates that the currencies referenced have been used as successor currencies replacing a previous currency in use.
-
C.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
-
D.
hasSettlementCurrency
Indicates that a financial transaction, contract, or account is settled using a specified 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aac14488190840b9c22209f13d1 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.