Triple
T33505030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward–Gatti II |
E858087
|
entity |
| Predicate | fighterStyleShowcased |
P165415
|
FINISHED |
| Object | Micky Ward’s pressure fighting |
—
|
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: Micky Ward’s pressure fighting | Statement: [Ward–Gatti II, fighterStyleShowcased, Micky Ward’s pressure fighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighterStyleShowcased Context triple: [Ward–Gatti II, fighterStyleShowcased, Micky Ward’s pressure fighting]
-
A.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
-
B.
fighter1Style
Indicates the fighting style or combat approach used by the first fighter in a matchup or comparison.
-
C.
fighter2Style
Indicates the fighting style or combat approach used by the second fighter in a matchup or interaction.
-
D.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
E.
styleOfBoxing
chosen
Indicates the specific boxing technique or approach that characterizes how an entity practices or performs boxing.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:38 a.m.