Triple
T25618045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roberto Durán in the 1980 "No Más" rematch |
E642210
|
entity |
| Predicate | fightType |
P161656
|
FINISHED |
| Object | rematch |
—
|
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: rematch | Statement: [Roberto Durán in the 1980 "No Más" rematch, fightType, rematch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightType Context triple: [Roberto Durán in the 1980 "No Más" rematch, fightType, rematch]
-
A.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
B.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
C.
fightingPreference
Indicates a relationship where one entity has a favored way, style, or choice of engaging in fights or combat relative to others.
-
D.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
E.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 21, 2026, 5:01 p.m.