Triple
T25028352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Standard Act of 1900 |
E626770
|
entity |
| Predicate | madeRedeemableIn |
P7021
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Gold Standard Act of 1900, madeRedeemableIn, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeRedeemableIn Context triple: [Gold Standard Act of 1900, madeRedeemableIn, gold]
-
A.
redeemableAt
chosen
Indicates that something (such as a voucher, coupon, or credit) can be exchanged for value or benefits at a specified place, platform, or entity.
-
B.
redeemabilityChangedTo
Indicates that the redeemability status of something has been updated or changed to a new specified state.
-
C.
notRedeemableFor
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
D.
canBeRedeemedFor
Indicates that one item, asset, or benefit may be exchanged or converted to obtain another specified item, asset, or benefit.
-
E.
redeemableByAct
Indicates that something (such as a right, claim, or instrument) can be redeemed, exercised, or satisfied through a specific formal act or legal action.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44f6c0538819084ae65fed91c4c86 |
completed | May 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:07 a.m.