Triple
T37463156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Living Mana |
E930967
|
entity |
| Predicate | counter |
P100355
|
FINISHED |
| Object | Area-of-effect damage spells |
—
|
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: Area-of-effect damage spells | Statement: [Living Mana, counter, Area-of-effect damage spells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counter Context triple: [Living Mana, counter, Area-of-effect damage spells]
-
A.
count
Indicates the numerical quantity or total number of instances of a specified entity or event.
-
B.
counterplay
chosen
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
C.
commonCounter
Indicates that two or more entities share the same counting mechanism, index, or tally used to track occurrences or quantities.
-
D.
counterMeasureAgainst
Indicates a relationship where one entity serves as a response or defensive action intended to prevent, mitigate, or neutralize the effects of another entity.
-
E.
counterSlogan
Indicates that one slogan is created or used specifically to oppose, refute, or undermine another slogan.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a036b0755888190a68a673664f0ea46 |
completed | May 12, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_6a036228676c8190aac9c90f7d8cedf7 |
completed | May 12, 2026, 5:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.