Triple
T15456326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Líf |
E371777
|
entity |
| Predicate | postEventWorld |
P118885
|
FINISHED |
| Object | renewed 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: renewed world after Ragnarök | Statement: [Líf, postEventWorld, renewed world after Ragnarök]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postEventWorld Context triple: [Líf, postEventWorld, renewed world after Ragnarök]
-
A.
publishedEvent
Indicates that an entity has formally released or made an event publicly available or announced.
-
B.
eventBroadcastOn
Indicates that an event is transmitted or made available through a particular broadcast channel, medium, or platform.
-
C.
peakEvent
Indicates the occurrence of a maximum or most intense point within a process, activity, or measurable phenomenon.
-
D.
postEventStatus
Indicates the status or condition assigned to an event after it has occurred or been processed.
-
E.
postBattleEvent
Indicates an event or occurrence that takes place after a battle has concluded.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f146a2c8190882741af3ec15268 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:31 a.m.