Triple
T17930808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of March 3, 1887 |
E448325
|
entity |
| Predicate | redemptionRate |
P129761
|
FINISHED |
| Object | face value |
—
|
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: face value | Statement: [Act of March 3, 1887, redemptionRate, face value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redemptionRate Context triple: [Act of March 3, 1887, redemptionRate, face value]
-
A.
redemptionFrequency
Indicates how often a redemption action or event occurs within a given time period.
-
B.
redemptionType
Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
-
C.
redemptionOptions
Indicates the ways or methods by which something (such as points, credits, or vouchers) can be redeemed or exchanged for value.
-
D.
redemptionCurrency
Indicates that one entity specifies the type of currency or medium used to redeem value, rewards, or benefits from another entity.
-
E.
redemptionStatus
Indicates whether something that was previously issued, owed, or reserved has been claimed, fulfilled, or otherwise redeemed.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a551e1788190abad0d6a85ec55e1 |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:20 a.m.