Triple
T12347901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meldrick Taylor |
E294404
|
entity |
| Predicate | fightOutcome |
P19109
|
FINISHED |
| Object | TKO loss to Julio César Chávez in 12th round |
—
|
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: TKO loss to Julio César Chávez in 12th round | Statement: [Meldrick Taylor, fightOutcome, TKO loss to Julio César Chávez in 12th round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightOutcome Context triple: [Meldrick Taylor, fightOutcome, TKO loss to Julio César Chávez in 12th round]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
-
C.
tacticalOutcome
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
-
D.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
defeat
Indicates that one entity wins against and overcomes 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7ba17481908b03af7316b28d9b |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.