Triple
T33549978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward–Gatti III |
E859305
|
entity |
| Predicate | styleOfFight |
P165415
|
FINISHED |
| Object | slugfest |
—
|
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: slugfest | Statement: [Ward–Gatti III, styleOfFight, slugfest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfFight Context triple: [Ward–Gatti III, styleOfFight, slugfest]
-
A.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
-
B.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
C.
styleOfBoxing
chosen
Indicates the specific boxing technique or approach that characterizes how an entity practices or performs boxing.
-
D.
打撃スタイル
Indicates a relationship where an entity is characterized by or associated with a particular style or manner of striking or hitting.
-
E.
fightingPreference
Indicates a relationship where one entity has a favored way, style, or choice of engaging in fights or combat relative to others.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:39 a.m.