Triple
T443852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape rixdollar |
E10173
|
entity |
| Predicate | monetaryStandard |
P5190
|
FINISHED |
| Object | silver-based currency |
—
|
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-based currency | Statement: [Cape rixdollar, monetaryStandard, silver-based currency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryStandard Context triple: [Cape rixdollar, monetaryStandard, silver-based currency]
-
A.
definedMonetarySystem
Indicates that an authority or entity has established and specified the rules, structure, and characteristics of a particular monetary system.
-
B.
currencyInitiative
Indicates an initiative, program, or action specifically related to the development, regulation, promotion, or reform of a currency or monetary system.
-
C.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
D.
monetaryComponent
chosen
Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
-
E.
successorMonetarySystem
Indicates that one monetary system directly follows and replaces another in time or function.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef43e8f88190a5d368add11a38c0 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.