Triple
T35867301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darkness Falls franchise |
E1037121
|
entity |
| Predicate | centralMythology |
P195614
|
FINISHED |
| Object | Tooth Fairy 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: Tooth Fairy curse | Statement: [Darkness Falls franchise, centralMythology, Tooth Fairy curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralMythology Context triple: [Darkness Falls franchise, centralMythology, Tooth Fairy curse]
-
A.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
B.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
D.
expandsMythologyOf
Indicates that one entity broadens, enriches, or adds new elements to the mythological background or lore associated with another entity.
-
E.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69fddac42c4081908568649058e86458 |
completed | May 8, 2026, 12:44 p.m. |
Created at: May 3, 2026, 4:06 p.m.