Triple
T37662655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Healing |
E937749
|
entity |
| Predicate | lingeringVariantEffect |
P189177
|
FINISHED |
| Object | creates healing cloud |
—
|
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: creates healing cloud | Statement: [Potion of Healing, lingeringVariantEffect, creates healing cloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lingeringVariantEffect Context triple: [Potion of Healing, lingeringVariantEffect, creates healing cloud]
-
A.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
B.
continuityVariant
Indicates that one entity is an alternative or modified version of another within the same narrative or continuity.
-
C.
lingeringID
Indicates that an entity continues to exist, remain present, or have an effect beyond the time or context in which it was originally expected to end or disappear.
-
D.
polymorphismEffect
Indicates how a specific genetic polymorphism alters the effect, function, or outcome of a biological process, treatment, or phenotype.
-
E.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbb9e69b7481909beaf8264d87c5e5 |
completed | May 6, 2026, 10 p.m. |
Created at: May 3, 2026, 4:18 p.m.