Triple
T23339373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rona Jaffe Foundation Writers’ Award |
E591692
|
entity |
| Predicate | monetaryValuePerRecipient |
P151926
|
FINISHED |
| Object | 30000 US dollars |
—
|
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: 30000 US dollars | Statement: [Rona Jaffe Foundation Writers’ Award, monetaryValuePerRecipient, 30000 US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryValuePerRecipient Context triple: [Rona Jaffe Foundation Writers’ Award, monetaryValuePerRecipient, 30000 US dollars]
-
A.
valueInCents
Indicates that one entity specifies the monetary value of another entity expressed in cents.
-
B.
rechargeRate
Indicates the rate or speed at which something restores or replenishes its capacity, energy, or resources over time.
-
C.
transactionFees
Indicates the fees charged or incurred as part of executing a financial transaction between parties.
-
D.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
E.
foreignTransactionFee
Indicates that a fee is charged for processing a transaction involving a foreign currency or occurring outside the cardholder’s home country.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198317f4c8190a557cacb86568d6c |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:17 p.m.