Triple
T37662721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Fire Resistance |
E937751
|
entity |
| Predicate | effectSource |
P196408
|
FINISHED |
| Object | Fire Resistance status effect |
—
|
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: Fire Resistance status effect | Statement: [Potion of Fire Resistance, effectSource, Fire Resistance status effect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectSource Context triple: [Potion of Fire Resistance, effectSource, Fire Resistance status effect]
-
A.
effectDescription
Indicates a textual explanation of the outcome, consequence, or impact resulting from an action, event, or condition.
-
B.
effectTrigger
Indicates that one event, condition, or action initiates or causes another effect to occur.
-
C.
effectCategory
Indicates the general type or classification of an effect that one entity has on another or on a system.
-
D.
effectCount
Indicates the number of distinct effects or outcomes associated with a given action, event, or entity.
-
E.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
- 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_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69fe30bb07d08190877539d5aa202d24 |
completed | May 8, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:18 p.m.