Triple
T37462632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalimos, Primal Lord |
E930955
|
entity |
| Predicate | providesEffectType |
P92873
|
FINISHED |
| Object | direct damage |
—
|
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: direct damage | Statement: [Kalimos, Primal Lord, providesEffectType, direct damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesEffectType Context triple: [Kalimos, Primal Lord, providesEffectType, direct damage]
-
A.
providesEffect
Indicates that one entity causes, delivers, or produces a particular effect or outcome on another entity.
-
B.
hasTypeOfEffect
chosen
Indicates that one entity produces, exhibits, or is associated with a particular kind or category of effect on another entity or context.
-
C.
usesEffectType
Indicates that an entity employs or is associated with a particular type or category of effect in its operation or behavior.
-
D.
hasUniqueEffect
Indicates that the related entity produces a distinct outcome or influence that is not shared or replicated by any other entity in the given context.
-
E.
hasEffectText
Indicates that a subject is associated with a textual description specifying its effect or impact.
- 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_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:17 p.m.