Triple
T5355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US dollar |
E105
|
entity |
| Predicate | isAnchorCurrencyFor |
P245
|
FINISHED |
| Object | many currency pegs |
—
|
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: many currency pegs | Statement: [US dollar, isAnchorCurrencyFor, many currency pegs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAnchorCurrencyFor Context triple: [US dollar, isAnchorCurrencyFor, many currency pegs]
-
A.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
B.
currency
chosen
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
C.
endowmentCurrency
Indicates the type of currency in which an endowment is denominated or valued.
-
D.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
-
E.
charteredIn
Indicates that an organization or entity has been formally established, authorized, or incorporated within a specified jurisdiction or location.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23c24b3d08190a714126292fd5479 |
completed | Feb. 28, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69a23998af288190855f0456740cbd51 |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.