Triple
T38645445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sludgefist |
E938701
|
entity |
| Predicate | enrageType |
P146447
|
FINISHED |
| Object | hard enrage timer |
—
|
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: hard enrage timer | Statement: [Sludgefist, enrageType, hard enrage timer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enrageType Context triple: [Sludgefist, enrageType, hard enrage timer]
-
A.
differenceFromEnrage
Indicates that one entity differs from another specifically in aspects related to anger, provocation, or the state of being enraged.
-
B.
becomesHostileWhen
Indicates that one entity starts to act with hostility toward another entity when a specified condition or trigger occurs.
-
C.
outburstType
chosen
Indicates the specific kind or category of outburst that occurred in a given situation.
-
D.
eraOfIncreasedIntensity
Indicates a period during which the level or strength of a particular activity, condition, or phenomenon becomes significantly higher than before.
-
E.
aggressiveness
Indicates a tendency or disposition of an entity to initiate hostile, forceful, or confrontational actions toward 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.