Triple
T35102352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBA (Super) super-middleweight title |
E1013053
|
entity |
| Predicate | fightOutcomeForAward |
P72340
|
FINISHED |
| Object | victory in sanctioned title bout |
—
|
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: victory in sanctioned title bout | Statement: [WBA (Super) super-middleweight title, fightOutcomeForAward, victory in sanctioned title bout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightOutcomeForAward Context triple: [WBA (Super) super-middleweight title, fightOutcomeForAward, victory in sanctioned title bout]
-
A.
championshipOutcome
chosen
Indicates the result or final standing of a competitor or team in a championship event.
-
B.
winnerThrows
Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
-
C.
winnerRound
Indicates that an entity is the one who won a particular round in a multi-round event or competition.
-
D.
winsFor
Indicates that one entity achieves victory or success on behalf of, or in favor of, another entity.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.