Triple
T37662591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Water Breathing |
E937748
|
entity |
| Predicate | statusEffectApplied |
P100810
|
FINISHED |
| Object | Water Breathing |
—
|
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: Water Breathing | Statement: [Potion of Water Breathing, statusEffectApplied, Water Breathing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusEffectApplied Context triple: [Potion of Water Breathing, statusEffectApplied, Water Breathing]
-
A.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
B.
instantEffect
Indicates that one event or action produces its effect immediately at the same moment it occurs, without any delay.
-
C.
hadEffectUntil
Indicates that an effect or condition held true up to a specific time or event, after which it no longer applied.
-
D.
specialEffect
Indicates that one entity produces, applies, or is associated with a distinctive, often non-standard effect on another entity or on an event.
-
E.
grantsStatusEffect
chosen
Indicates that one entity applies or bestows a specific status effect onto another entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:18 p.m.