Triple
T6849540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azumah Nelson |
E157979
|
entity |
| Predicate | resultAgainstWilfredoGómez |
P18721
|
FINISHED |
| Object | won WBC featherweight title |
—
|
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: won WBC featherweight title | Statement: [Azumah Nelson, resultAgainstWilfredoGómez, won WBC featherweight title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAgainstWilfredoGómez Context triple: [Azumah Nelson, resultAgainstWilfredoGómez, won WBC featherweight title]
-
A.
wonAgainst
Indicates that one entity achieved victory over another in a competition, conflict, or contest.
-
B.
wonChampionshipAgainst
chosen
Indicates that one competitor secured a championship title by defeating another specific opponent.
-
C.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
D.
finalBoutLoser
Indicates that an entity is the competitor who lost in the final bout of a match, tournament, or competition.
-
E.
wonTournament
Indicates that an entity emerged as the overall victor in a tournament 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d84acb288190a67d974197ecab2f |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.