Triple
T36044165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collins family curse |
E1042622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional curse |
C33718
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: fictional curse Context triple: [Collins family curse, instanceOf, fictional curse]
-
A.
legendary curse
chosen
A legendary curse is a powerful, often ancient malediction tied to myth or history that brings enduring misfortune or supernatural consequences to those who invoke, inherit, or encounter it.
-
B.
fictional phenomenon
A fictional phenomenon is an imagined event, process, or occurrence that exists only within the context of a narrative or invented world, governed by that setting’s own internal logic rather than real-world science.
-
C.
fictional stage magic trick
A fictional stage magic trick is an imagined performance illusion, often impossible or exaggerated beyond real-world constraints, designed to astonish an audience within a narrative.
-
D.
cursed human
A cursed human is an individual whose body, mind, or fate has been irreversibly altered by a supernatural malediction, granting them burdensome powers, afflictions, or destinies beyond normal human experience.
-
E.
fictional daemon
A fictional daemon is a supernatural entity, often malevolent or mischievous, that exists within a narrative world to influence events, tempt characters, or embody abstract fears and desires.
- F. None of above.
Provenance (1 batch)
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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.