Triple
T12512266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jermain Taylor |
E299107
|
entity |
| Predicate | resultAgainstBernardHopkinsII |
P56461
|
FINISHED |
| Object | win by unanimous decision |
—
|
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: win by unanimous decision | Statement: [Jermain Taylor, resultAgainstBernardHopkinsII, win by unanimous decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAgainstBernardHopkinsII Context triple: [Jermain Taylor, resultAgainstBernardHopkinsII, win by unanimous decision]
-
A.
secondRoundWinner
Indicates that the subject is the winner of the second round in a multi-round competition, contest, or process.
-
B.
fightOutcomeWithRockyInRockyII
Indicates the outcome of a fight involving Rocky in the context of the movie Rocky II.
-
C.
resultOfMatch
chosen
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
D.
resultOfSecondAttack
Indicates that an event or state occurs as a consequence of a second attack in a sequence of attacks.
-
E.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.