Triple
T466632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British West Indies dollar |
E8460
|
entity |
| Predicate | currencyCodeStatus |
P15021
|
FINISHED |
| Object | no longer in use |
—
|
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: no longer in use | Statement: [British West Indies dollar, currencyCodeStatus, no longer in use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyCodeStatus Context triple: [British West Indies dollar, currencyCodeStatus, no longer in use]
-
A.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
currencyModel
Indicates that something uses, is based on, or conforms to a particular system or model of currency (e.g., monetary structure, denomination scheme, or valuation framework).
-
C.
codeNumericISO4217
Indicates that an entity is associated with a specific ISO 4217 numeric currency code.
-
D.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
-
E.
currencyNameEnglish
Indicates the English-language name used to refer to a given currency.
- F. None of above. chosen
Provenance (4 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd831088190b6ac6a56b34a8816 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef611b9c8190ac5e9174744d9127 |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.