Triple
T566969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Marathon Majors |
E13573
|
entity |
| Predicate | prizeStructure |
P10713
|
FINISHED |
| Object | series jackpot (historically) |
—
|
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: series jackpot (historically) | Statement: [World Marathon Majors, prizeStructure, series jackpot (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prizeStructure Context triple: [World Marathon Majors, prizeStructure, series jackpot (historically)]
-
A.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
B.
prizeContext
chosen
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
-
C.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
D.
prizePool
Indicates that a certain amount of rewards or funds is collectively available to be distributed among participants in an event, competition, or activity.
-
E.
typicalAwardComponents
Indicates the standard elements or parts that commonly make up a particular award.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b01aca48190944408d066519149 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.