Triple
T26675508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castillo vs. Mayweather I |
E672443
|
entity |
| Predicate | rematch |
P63572
|
FINISHED |
| Object | Castillo vs. Mayweather II |
—
|
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: Castillo vs. Mayweather II | Statement: [Castillo vs. Mayweather I, rematch, Castillo vs. Mayweather II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rematch Context triple: [Castillo vs. Mayweather I, rematch, Castillo vs. Mayweather II]
-
A.
rematchDate
Indicates the date on which a subsequent or repeat contest between the same parties is scheduled or took place.
-
B.
wasRematchOf
chosen
Indicates that an event or contest is a subsequent encounter between the same parties, held as a repeat of a previous matchup.
-
C.
isRematchOfFinal
Indicates that a match is a subsequent encounter replaying the same opponents and stakes as a previous final match.
-
D.
comebackWin
Indicates a victory achieved by overcoming a prior deficit or losing position during the contest or event.
-
E.
repeatStrikeOnRescuers
Indicates that an entity carries out multiple or ongoing attacks specifically targeting rescuers.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61702ad548190bbc5995748b3ffd2 |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:16 a.m.