Triple
T37552912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frostmourne |
E933628
|
entity |
| Predicate | effectOnWielder |
P196106
|
FINISHED |
| Object | corrupts the wielder’s mind |
—
|
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: corrupts the wielder’s mind | Statement: [Frostmourne, effectOnWielder, corrupts the wielder’s mind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnWielder Context triple: [Frostmourne, effectOnWielder, corrupts the wielder’s mind]
-
A.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
B.
weaponAffected
Indicates that one entity is a weapon that has an effect on, or causes a change to, another entity.
-
C.
effectCategory
Indicates the general type or classification of an effect that one entity has on another or on a system.
-
D.
effectTrigger
Indicates that one event, condition, or action initiates or causes another effect to occur.
-
E.
effectDescription
chosen
Indicates a textual explanation of the outcome, consequence, or impact resulting from an action, event, or condition.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:17 p.m.