Triple
T36317140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hödur |
E894227
|
entity |
| Predicate | trickedInto |
P7322
|
FINISHED |
| Object | killing Baldr with mistletoe |
—
|
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: killing Baldr with mistletoe | Statement: [Hödur, trickedInto, killing Baldr with mistletoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trickedInto Context triple: [Hödur, trickedInto, killing Baldr with mistletoe]
-
A.
tricked
chosen
Indicates that one entity intentionally deceived another into believing something false or acting under a false impression.
-
B.
intrudedInto
Indicates that one entity has entered or encroached upon another entity’s space, domain, or context without permission or in an unwelcome manner.
-
C.
trappedWith
Indicates that two or more entities are confined together in the same restricted space or situation, unable to leave independently.
-
D.
trap
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
-
E.
trappedIn
Indicates that one entity is confined or caught within another entity or bounded space, unable to leave freely.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.