Triple
T37662642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Healing |
E937749
|
entity |
| Predicate | opposesEffect |
P149536
|
FINISHED |
| Object | Potion of Harming |
—
|
NE NERFINISHED |
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: Potion of Harming | Statement: [Potion of Healing, opposesEffect, Potion of Harming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesEffect Context triple: [Potion of Healing, opposesEffect, Potion of Harming]
-
A.
opposesEffectOf
chosen
Indicates that one entity counteracts, reduces, or nullifies the effect produced by another entity.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opposedOutcome
Indicates that one entity’s outcome is in conflict with, counters, or works against the outcome associated with another entity.
-
D.
opposedFocus
Indicates that one entity’s focus, attention, or emphasis is directed in opposition to, or in contrast with, the focus of another entity.
-
E.
inhibitionEffect
Indicates that one entity reduces, blocks, or suppresses the activity, effect, or occurrence of 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_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:18 p.m.