Triple
T25307838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily Derby |
E634528
|
entity |
| Predicate | payoutForm |
P158372
|
FINISHED |
| Object | lump-sum cash |
—
|
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: lump-sum cash | Statement: [Daily Derby, payoutForm, lump-sum cash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payoutForm Context triple: [Daily Derby, payoutForm, lump-sum cash]
-
A.
payableFrom
Indicates that a payment or monetary obligation is sourced, funded, or discharged from a specified account, entity, or resource.
-
B.
paymasterGeneral
Indicates a relationship where one entity serves as the chief official responsible for authorizing or overseeing payments on behalf of another entity or organization.
-
C.
pays
Indicates that one entity gives money or another form of compensation to another entity, typically in exchange for goods, services, or to settle a debt.
-
D.
payReform
Indicates a relationship where an authority changes or restructures the pay system, such as salaries or compensation terms, for a group of people.
-
E.
paysAfter
Indicates that one entity makes a payment to another entity only after a specified event, condition, or time has occurred.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939c49a48190b9fdc2555273915e |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:25 p.m.