Triple
T15393829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gleipnir |
E368116
|
entity |
| Predicate | statusAtRagnarök |
P118607
|
FINISHED |
| Object | brokenWhenFenrirFreesHimself |
—
|
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: brokenWhenFenrirFreesHimself | Statement: [Gleipnir, statusAtRagnarök, brokenWhenFenrirFreesHimself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAtRagnarök Context triple: [Gleipnir, statusAtRagnarök, brokenWhenFenrirFreesHimself]
-
A.
actionAtRagnarök
Indicates an action or event that is specifically performed or occurs during Ragnarök, the final apocalyptic battle in Norse mythology.
-
B.
eventualSideAtRagnarök
Indicates the side or faction an entity will ultimately align with or belong to during Ragnarök.
-
C.
leadsAtRagnarök
Indicates that the subject serves as a leader or commanding figure specifically during the events of Ragnarök.
-
D.
roleAfterRagnarök
Indicates the role, status, or function an entity will have after the events of Ragnarök have occurred.
-
E.
statusAfterBattleForAzeroth
Indicates the condition or state of an entity following the events of the Battle for Azeroth.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
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:19 a.m.