Triple
T17662596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Pegasus World Cup Invitational Stakes |
E440288
|
entity |
| Predicate | totalPurse |
P128453
|
FINISHED |
| Object | 12000000 USD |
—
|
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: 12000000 USD | Statement: [2017 Pegasus World Cup Invitational Stakes, totalPurse, 12000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalPurse Context triple: [2017 Pegasus World Cup Invitational Stakes, totalPurse, 12000000 USD]
-
A.
approximatePurse
Indicates that one entity estimates or comes close to determining the value, amount, or contents of another entity’s purse or collection of resources.
-
B.
currencyOfPurse
Indicates the type of currency that is contained in or associated with a given purse.
-
C.
purse
Indicates attempting to influence or persuade someone to adopt a particular course of action, belief, or decision.
-
D.
purseRecord
Indicates a record or log entry that captures the state, contents, or transactions associated with a purse or similar container of funds.
-
E.
MoneyInTheBankCashInBy
Indicates that a Money in the Bank contract is cashed in by a particular person or entity.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea73c90819087a23a7b6171f581 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 9:51 a.m.