Triple
T10913340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höðr |
E257754
|
entity |
| Predicate | statusAfterRagnarök |
P95063
|
FINISHED |
| Object | uncertain in surviving sources |
—
|
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: uncertain in surviving sources | Statement: [Höðr, statusAfterRagnarök, uncertain in surviving sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterRagnarök Context triple: [Höðr, statusAfterRagnarök, uncertain in surviving sources]
-
A.
roleAfterRagnarök
chosen
Indicates the role, status, or function an entity will have after the events of Ragnarök have occurred.
-
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.
statusAfterBattleOfFiveArmies
Indicates the condition or state of an entity following the events of the Battle of Five Armies.
-
E.
statusAfterSmaug
Indicates the resulting status or condition of an entity after an event or interaction involving Smaug has occurred.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7707310b0819092d0140acc3c64ba |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.