Triple
T26008149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Hearns vs Sugar Ray Leonard I (1981) |
E646815
|
entity |
| Predicate | purseFighter1ApproxUSD |
P131010
|
FINISHED |
| Object | 10000000 |
—
|
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: 10000000 | Statement: [Thomas Hearns vs Sugar Ray Leonard I (1981), purseFighter1ApproxUSD, 10000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purseFighter1ApproxUSD Context triple: [Thomas Hearns vs Sugar Ray Leonard I (1981), purseFighter1ApproxUSD, 10000000]
-
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.
typicalPurseRangeUSD
chosen
Indicates the usual monetary range in U.S. dollars for the prize purse or total payout associated with an event or activity.
-
C.
purse
Indicates attempting to influence or persuade someone to adopt a particular course of action, belief, or decision.
-
D.
purseType
Indicates the specific kind or category of purse associated with an entity.
-
E.
currencyOfPurse
Indicates the type of currency that is contained in or associated with a given purse.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605b366f8819096534cffdd0aa509 |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:01 a.m.