Triple
T35081626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamia (Drag Me to Hell) |
E1012451
|
entity |
| Predicate | methodOfClaimingSoul |
P26671
|
FINISHED |
| Object | dragging victim to hell |
—
|
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: dragging victim to hell | Statement: [Lamia (Drag Me to Hell), methodOfClaimingSoul, dragging victim to hell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfClaimingSoul Context triple: [Lamia (Drag Me to Hell), methodOfClaimingSoul, dragging victim to hell]
-
A.
methodOfResurrection
Indicates the specific process or means by which an entity is brought back to life or restored from death.
-
B.
receivesSoulsOf
chosen
Indicates that one entity takes in or accepts the souls of another entity or group of entities.
-
C.
soulReincarnatedAs
Indicates that a soul, after death or departure from a previous existence, is reborn into a new body or form.
-
D.
methodOfSummoning
Indicates the specific way or procedure by which an entity is called forth, invoked, or brought into presence.
-
E.
associatedWithPositionThroughSoul
Indicates a relationship where an entity’s position, role, or placement is determined or influenced through its soul or spiritual essence.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.