Triple
T30112311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thackery Binx (human form) in Hocus Pocus |
E765313
|
entity |
| Predicate | reasonForSurvival |
P186376
|
FINISHED |
| Object | immortality curse |
—
|
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: immortality curse | Statement: [Thackery Binx (human form) in Hocus Pocus, reasonForSurvival, immortality curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForSurvival Context triple: [Thackery Binx (human form) in Hocus Pocus, reasonForSurvival, immortality curse]
-
A.
survivalTheme
Indicates that the relationship or situation centers on the struggle to stay alive or endure extreme hardship.
-
B.
helpsSurvive
Indicates that one entity provides support or advantage that increases another entity’s chances of survival.
-
C.
survivedDisaster
Indicates that an entity continued to live or exist after experiencing and enduring a disaster.
-
D.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
E.
worksSurvival
Indicates that one entity’s work or effort enables, supports, or is necessary for another entity’s survival.
- F. None of above. chosen
Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 29, 2026, 7:10 p.m.