Triple
T38593048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Blossom |
E932496
|
entity |
| Predicate | teamfightImpact |
P52396
|
FINISHED |
| Object | fight-winning potential |
—
|
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: fight-winning potential | Statement: [Death Blossom, teamfightImpact, fight-winning potential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamfightImpact Context triple: [Death Blossom, teamfightImpact, fight-winning potential]
-
A.
gameplayImpact
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
B.
championWins
Indicates that a champion emerges victorious in a competition, match, or contest.
-
C.
fightingAttribute
Indicates a relationship where one entity’s characteristics or properties are associated with combat or fighting-related capabilities of another entity.
-
D.
championInvolved
Indicates that a champion (or leading figure) is actively participating in or associated with the specified event, activity, or context.
-
E.
impactOnField
chosen
Indicates the effect or influence that one entity, action, or development has on a particular field or domain.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.