Triple
T7828721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Basketball Tournament |
E181310
|
entity |
| Predicate | winnerTakeAllPrize |
P14849
|
FINISHED |
| Object | 1,000,000 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: 1,000,000 USD | Statement: [The Basketball Tournament, winnerTakeAllPrize, 1,000,000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerTakeAllPrize Context triple: [The Basketball Tournament, winnerTakeAllPrize, 1,000,000 USD]
-
A.
winnerTakeAll
Indicates that one participant receives all the benefits, rewards, or outcomes from a competition or situation, leaving none for the others.
-
B.
winnerReceives
chosen
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
C.
winnerMake
Indicates that one entity causes or brings about another entity becoming the winner in a contest, competition, or selection process.
-
D.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
E.
winnerRight
Indicates that the referenced entity is the winner on the right side or right position in a competitive or comparative 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04aaed1881908e1da129a43ef9c7 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:43 p.m.