Triple
T25528693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Kelley |
E639848
|
entity |
| Predicate | notableFightType |
P161656
|
FINISHED |
| Object | featherweight bout |
—
|
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: featherweight bout | Statement: [Kevin Kelley, notableFightType, featherweight bout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFightType Context triple: [Kevin Kelley, notableFightType, featherweight bout]
-
A.
notableFightSeries
Indicates that there is a recurring or thematically linked series of fights or battles associated with the subject.
-
B.
bearerNotableFight
Indicates that the bearer has participated in a specific fight or combat event that is considered notable or significant.
-
C.
fightType
chosen
Indicates the specific category or style of fight associated with an event or interaction between entities.
-
D.
isWorldChampionshipFight
Indicates that a given fight is officially recognized as a world championship bout for a title in its sport.
-
E.
notableWinType
Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 21, 2026, 3:12 p.m.