Triple
T29072574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiian dollar |
E735848
|
entity |
| Predicate | valuePeggedTo |
P26645
|
FINISHED |
| Object | United States dollar |
—
|
NE NERFINISHED |
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: United States dollar | Statement: [Hawaiian dollar, valuePeggedTo, United States dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valuePeggedTo Context triple: [Hawaiian dollar, valuePeggedTo, United States dollar]
-
A.
isPegged
Indicates that one entity’s value, status, or behavior is fixed or tightly linked to that of another entity, typically so that changes in the reference entity directly determine changes in the pegged entity.
-
B.
currencyPeg
chosen
Indicates that one currency’s value is fixed or tightly linked to the value of another currency or a basket of currencies.
-
C.
valueRelativeToGuilder
Indicates that something’s value is expressed in terms of, or compared relative to, the guilder currency.
-
D.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
E.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 10:20 a.m.