Triple
T14843205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Wilderness |
E349017
|
entity |
| Predicate | hasMythImpact |
P116045
|
FINISHED |
| Object | popularization of lemming suicide misconception |
—
|
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: popularization of lemming suicide misconception | Statement: [White Wilderness, hasMythImpact, popularization of lemming suicide misconception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythImpact Context triple: [White Wilderness, hasMythImpact, popularization of lemming suicide misconception]
-
A.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
B.
hasMythSource
Indicates that something derives from, is based on, or is supported by a particular myth or mythological source.
-
C.
hasMythicSetting
Indicates that something is set within a mythic, legendary, or folklore-based world or context.
-
D.
hasMythicEvent
Indicates that an entity is associated with, involves, or features a significant mythic or legendary event.
-
E.
hasMythicFunction
Indicates that something serves a symbolic, narrative, or ritual role within a mythic or mythological framework.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded28fa49c81908d1059e6cafd607f |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:53 a.m.