Triple
T38592466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulse Bomb |
E932484
|
entity |
| Predicate | canBeAvoidedBy |
P82365
|
FINISHED |
| Object | Reaper Wraith Form |
—
|
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: Reaper Wraith Form | Statement: [Pulse Bomb, canBeAvoidedBy, Reaper Wraith Form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAvoidedBy Context triple: [Pulse Bomb, canBeAvoidedBy, Reaper Wraith Form]
-
A.
designedToBeAvoided
Indicates that something is intentionally created or arranged in a way that people should avoid using, encountering, or engaging with it.
-
B.
avoidedFor
Indicates that one entity is deliberately not used, chosen, or engaged with because of the presence, influence, or characteristics of another entity.
-
C.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
D.
seeksToAvoid
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
E.
isPreventableBy
chosen
Indicates that the occurrence or effect of one entity can be avoided or stopped through the action, intervention, or influence 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:32 p.m.