Triple
T1370682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne Cup |
E30105
|
entity |
| Predicate | approximatePrizeMoney |
P15222
|
FINISHED |
| Object | multi-million Australian 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: multi-million Australian dollars | Statement: [Melbourne Cup, approximatePrizeMoney, multi-million Australian dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePrizeMoney Context triple: [Melbourne Cup, approximatePrizeMoney, multi-million Australian dollars]
-
A.
typicalAwardAmount
Indicates the usual or most common amount of an award given in this relationship.
-
B.
awardAmount
Indicates the specific quantity or value of an award that is granted in the context of a particular awarding event or relationship.
-
C.
prizePool
chosen
Indicates that a certain amount of rewards or funds is collectively available to be distributed among participants in an event, competition, or activity.
-
D.
prizeContext
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
-
E.
positionAwarded
Indicates that a specific position, role, or title has been formally granted to an entity (such as a person or organization).
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d7b6008190bc0303b56959ba56 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.