Triple
T33193115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Johnson vs. James J. Jeffries |
E849665
|
entity |
| Predicate | purseLoserShare |
P176802
|
FINISHED |
| Object | 10000 |
—
|
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: 10000 | Statement: [Jack Johnson vs. James J. Jeffries, purseLoserShare, 10000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purseLoserShare Context triple: [Jack Johnson vs. James J. Jeffries, purseLoserShare, 10000]
-
A.
purseFighter2ApproxUSD
Indicates the approximate amount of money, in US dollars, awarded or paid to the second fighter in a bout.
-
B.
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.
-
C.
purseRecord
Indicates a record or log entry that captures the state, contents, or transactions associated with a purse or similar container of funds.
-
D.
totalPurse
Indicates the total amount of prize money or winnings available in a given competitive event or context.
-
E.
purseContext
Indicates the situational or environmental context in which a purse is used, referenced, or relevant.
- F. None of above. chosen
Provenance (4 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:29 a.m.