Triple
T25677561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gene Fullmer |
E643847
|
entity |
| Predicate | rematchOpponent |
P63572
|
FINISHED |
| Object | Sugar Ray Robinson |
—
|
NE NERFINISHED |
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: Sugar Ray Robinson | Statement: [Gene Fullmer, rematchOpponent, Sugar Ray Robinson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rematchOpponent Context triple: [Gene Fullmer, rematchOpponent, Sugar Ray Robinson]
-
A.
wasRematchOf
chosen
Indicates that an event or contest is a subsequent encounter between the same parties, held as a repeat of a previous matchup.
-
B.
rematchDate
Indicates the date on which a subsequent or repeat contest between the same parties is scheduled or took place.
-
C.
thirdRoundReplayOpponent
Indicates that one entity is the opponent faced by another entity in a replay match of the third round of a competition or tournament.
-
D.
laterOpponent
Indicates that one entity becomes the opponent of another at a later time or stage, following an earlier phase or matchup.
-
E.
isRematchOfFinal
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb7700888190a773a390033bf320 |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:41 p.m.