Triple
T10626941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Móði |
E250347
|
entity |
| Predicate | roleAfterRagnarök |
P95063
|
FINISHED |
| Object | new world after Ragnarök |
—
|
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: new world after Ragnarök | Statement: [Móði, roleAfterRagnarök, new world after Ragnarök]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAfterRagnarök Context triple: [Móði, roleAfterRagnarök, new world after Ragnarök]
-
A.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
B.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
-
C.
roleAfterAlexander
Indicates that one entity holds a role, position, or status that is defined or understood specifically in the context of the period after Alexander (typically Alexander the Great).
-
D.
eventualSideAtRagnarök
Indicates the side or faction an entity will ultimately align with or belong to during Ragnarök.
-
E.
roleInThor
Indicates that an entity has a specific role or character assignment in the context of the work "Thor."
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df8207f08190a6362a8ba00988b2 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 8:55 p.m.