Triple
T3473999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freyr |
E73326
|
entity |
| Predicate | foretoldEvent |
P22416
|
FINISHED |
| Object | death at Ragnarok |
—
|
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: death at Ragnarok | Statement: [Freyr, foretoldEvent, death at Ragnarok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foretoldEvent Context triple: [Freyr, foretoldEvent, death at Ragnarok]
-
A.
eschatologicalEvent
Indicates an event associated with ultimate destiny or final outcomes in a religious or philosophical end-times framework.
-
B.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
C.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
D.
subjectOfProphecy
chosen
Indicates that the subject is foretold or predicted to play a significant role or experience a specific event according to a prophecy.
-
E.
prophecyOverheardBy
Indicates that a prophecy was heard or accidentally listened to by a particular entity, without necessarily being its intended recipient.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3e03e081908aa09291bbf351bd |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.