Triple
T37461167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ragnaros, Lightlord |
E930919
|
entity |
| Predicate | endOfTurnEffect |
P187929
|
FINISHED |
| Object | Restore 8 Health to a damaged friendly character |
—
|
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: Restore 8 Health to a damaged friendly character | Statement: [Ragnaros, Lightlord, endOfTurnEffect, Restore 8 Health to a damaged friendly character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfTurnEffect Context triple: [Ragnaros, Lightlord, endOfTurnEffect, Restore 8 Health to a damaged friendly character]
-
A.
opponentActionEnded
Indicates that an opposing party’s action or move has been completed or has come to an end.
-
B.
terminateEffect
Indicates that an ongoing effect, condition, or process is brought to an end or cancelled.
-
C.
endOfMovement
Indicates the point or moment at which a movement, action, or motion comes to a stop or is completed.
-
D.
endOfActivity
Indicates that a particular activity has reached its completion or final point in time.
-
E.
endLocalTimeEffect
Indicates the point in local time at which a particular condition, event, or effect stops being in force.
- F. None of above. chosen
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.