Triple
T31572503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dempsey–Tunney boxing matches |
E805601
|
entity |
| Predicate | featuredFighterStyleContrast |
P202458
|
FINISHED |
| Object | slugger vs boxer |
—
|
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: slugger vs boxer | Statement: [Dempsey–Tunney boxing matches, featuredFighterStyleContrast, slugger vs boxer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredFighterStyleContrast Context triple: [Dempsey–Tunney boxing matches, featuredFighterStyleContrast, slugger vs boxer]
-
A.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
-
B.
featuredFighter
Indicates that a particular fighter is highlighted or prominently showcased in a given context or event.
-
C.
fighter1Style
Indicates the fighting style or combat approach used by the first fighter in a matchup or comparison.
-
D.
styleOfBoxing
Indicates the specific boxing technique or approach that characterizes how an entity practices or performs boxing.
-
E.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
- F. None of above. chosen
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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00818b20a881909fbf3bb33dcf7029 |
completed | May 10, 2026, 1 p.m. |
| PD | Predicate disambiguation | batch_6a0080f76f588190a933238861243d1a |
completed | May 10, 2026, 12:58 p.m. |
| PDg | Predicate description generation | batch_6a00818a671c819086d487dd5a5ba5d7 |
completed | May 10, 2026, 1 p.m. |
Created at: April 30, 2026, 10:20 p.m.