Triple
T37763498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imprisoned Demons |
E941347
|
entity |
| Predicate | awakeningEffect |
P53074
|
FINISHED |
| Object | trigger a powerful effect when awakening |
—
|
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: trigger a powerful effect when awakening | Statement: [Imprisoned Demons, awakeningEffect, trigger a powerful effect when awakening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awakeningEffect Context triple: [Imprisoned Demons, awakeningEffect, trigger a powerful effect when awakening]
-
A.
awakeningEvent
Indicates an event in which an entity transitions from a state of sleep, inactivity, or unawareness to a state of wakefulness, activity, or awareness.
-
B.
awakensIn
Indicates that one entity comes out of sleep or becomes conscious while located within or inside another entity.
-
C.
awakensBy
Indicates that one entity causes another entity to wake up from sleep or inactivity.
-
D.
awakensBefore
Indicates that one entity wakes up earlier in time than another entity.
-
E.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.