Triple
T33549944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward–Gatti III |
E859305
|
entity |
| Predicate | featuresBoxerInBlueCorner |
P101800
|
FINISHED |
| Object | Micky Ward |
E244200
|
NE 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: Micky Ward | Statement: [Ward–Gatti III, featuresBoxerInBlueCorner, Micky Ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBoxerInBlueCorner Context triple: [Ward–Gatti III, featuresBoxerInBlueCorner, Micky Ward]
-
A.
winningBoxer
Indicates that one boxer has defeated another in a boxing match and is recognized as the winner.
-
B.
losingBoxer
Indicates that the subject is the boxer who is defeated or on the losing side in a boxing match.
-
C.
typeOfBoxer
Indicates the specific category or style of boxer that an individual belongs to.
-
D.
featuredFighter
chosen
Indicates that a particular fighter is highlighted or prominently showcased in a given context or event.
-
E.
hasFighterInRedCorner
Indicates that a specified match or event has a particular fighter assigned to the red corner.
- F. None of above.
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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01c41dfe248190a68f4a262591b30f |
completed | May 11, 2026, 11:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36a00f5cd88190a5aef8c90dcaaf59 |
completed | June 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a01c375d14c8190a15bfa12623588a9 |
completed | May 11, 2026, 11:54 a.m. |
Created at: May 1, 2026, 1:39 a.m.