Triple
T4386459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belmont Stakes |
E99253
|
entity |
| Predicate | typicalPurse |
P39152
|
FINISHED |
| Object | 1500000 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: 1500000 USD | Statement: [Belmont Stakes, typicalPurse, 1500000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPurse Context triple: [Belmont Stakes, typicalPurse, 1500000 USD]
-
A.
purse
Indicates attempting to influence or persuade someone to adopt a particular course of action, belief, or decision.
-
B.
purseRecord
Indicates a record or log entry that captures the state, contents, or transactions associated with a purse or similar container of funds.
-
C.
typicallyHolds
chosen
Indicates that a certain relationship or condition generally holds true in typical or normal situations, though not necessarily in all cases.
-
D.
currencyOfPurse
Indicates the type of currency that is contained in or associated with a given purse.
-
E.
purseGeorgeForeman
Indicates that an entity is pursuing, seeking, or going after George Foreman, typically in a competitive, legal, or goal-oriented context.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352669f608190b3aa7030d8073e04 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.