Triple
T37664605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skeleton (Java Edition, certain conditions) |
E937792
|
entity |
| Predicate | affectedByPotion |
P190417
|
FINISHED |
| Object | Instant Damage heals |
—
|
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: Instant Damage heals | Statement: [Skeleton (Java Edition, certain conditions), affectedByPotion, Instant Damage heals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedByPotion Context triple: [Skeleton (Java Edition, certain conditions), affectedByPotion, Instant Damage heals]
-
A.
givesPotionTo
Indicates that one entity provides or hands over a potion to another entity.
-
B.
affectedByMagicCoat
Indicates that an action or effect directed at an entity is reflected back to its originator due to the influence of a "Magic Coat"-like protective effect.
-
C.
basePotion
Indicates that one entity serves as the foundational or primary potion from which another potion or effect is derived.
-
D.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
E.
affectedBySpellDamage
Indicates that an entity receives or is impacted by damage resulting from a spell.
- 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_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc4b5f22c8190b8b256adbdc2570c |
completed | May 7, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:18 p.m.