Triple
T24944559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIBA World Boxing Championships |
E624150
|
entity |
| Predicate | boutOutcomeTypes |
P156831
|
FINISHED |
| Object | referee stoppage |
—
|
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: referee stoppage | Statement: [AIBA World Boxing Championships, boutOutcomeTypes, referee stoppage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boutOutcomeTypes Context triple: [AIBA World Boxing Championships, boutOutcomeTypes, referee stoppage]
-
A.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
B.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
boutType
Indicates the specific category or format of a competitive bout (such as its ruleset, level, or style) that characterizes how the contest is conducted.
-
D.
playerOutcome
Indicates the result or consequence experienced by a player in a game, match, or scenario (such as winning, losing, or drawing).
-
E.
commonMatchOutcomeTypes
chosen
Indicates that the related entities share the same typical or frequently occurring types of outcomes for a match or contest.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:53 a.m.