Triple
T3510771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muspelheim |
E74188
|
entity |
| Predicate | mythicOpposition |
P21665
|
FINISHED |
| Object | world of ice Niflheim |
—
|
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: world of ice Niflheim | Statement: [Muspelheim, mythicOpposition, world of ice Niflheim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythicOpposition Context triple: [Muspelheim, mythicOpposition, world of ice Niflheim]
-
A.
typeOfOpposition
Indicates a relationship where one entity stands in opposition or contrast to another, such as being a rival, adversary, or countering force.
-
B.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
hasConceptualOpposite
chosen
Indicates that one entity represents a concept that is fundamentally opposed or contrary in meaning to the concept represented by another entity.
-
D.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
E.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc0f6cf8819098a1ec8693cc50e7 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.