Triple
T19464253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hodr |
E486951
|
entity |
| Predicate | postRagnarokRole |
P95063
|
FINISHED |
| Object | dwells in new world with surviving gods |
—
|
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: dwells in new world with surviving gods | Statement: [Hodr, postRagnarokRole, dwells in new world with surviving gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRagnarokRole Context triple: [Hodr, postRagnarokRole, dwells in new world with surviving gods]
-
A.
roleAtRagnarok
Indicates the specific function, position, or part an entity is expected to have or perform during Ragnarok.
-
B.
postHunnicRole
Indicates the role, position, or function an entity held in the period following the decline or end of Hunnic dominance.
-
C.
roleAfterRagnarök
chosen
Indicates the role, status, or function an entity will have after the events of Ragnarök have occurred.
-
D.
postGideonRole
Indicates the role or position an entity holds after the event or period associated with Gideon.
-
E.
roleInWarcraft
Indicates that an entity has a specific character, class, or functional role within the Warcraft universe or game setting.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633cf95988190b13b2153e67d0cac |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.