Triple
T37463051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Mosh |
E930965
|
entity |
| Predicate | classSynergy |
P189406
|
FINISHED |
| Object | Warrior damage effects |
—
|
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: Warrior damage effects | Statement: [King Mosh, classSynergy, Warrior damage effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classSynergy Context triple: [King Mosh, classSynergy, Warrior damage effects]
-
A.
classTribeSynergy
Indicates a synergistic relationship where a character’s class and tribe traits interact to provide combined or enhanced effects.
-
B.
raceSynergy
Indicates how the combination of different races or species enhances, modifies, or interacts to affect overall effectiveness or outcome.
-
C.
synergyCondition
Indicates that a specific set of conditions must be met for multiple entities or actions to interact in a mutually enhancing or combined-effect manner.
-
D.
actsSynergisticallyWith
Indicates that two entities interact in a way that enhances or amplifies each other's effects or outcomes beyond what they would achieve independently.
-
E.
heroClassSynergy
chosen
Indicates a beneficial interaction or combined effect that occurs when specific hero classes are used together.
- 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_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:17 p.m.