Triple
T15393833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gleipnir |
E368116
|
entity |
| Predicate | requiresCondition |
P100
|
FINISHED |
| Object | TýrPlacingHandInFenrir’sMouth |
E73465
|
NE 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: TýrPlacingHandInFenrir’sMouth | Statement: [Gleipnir, requiresCondition, TýrPlacingHandInFenrir’sMouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TýrPlacingHandInFenrir’sMouth Context triple: [Gleipnir, requiresCondition, TýrPlacingHandInFenrir’sMouth]
-
A.
Fenrir
Fenrir is a monstrous wolf in Norse mythology prophesied to kill the god Odin during Ragnarök.
-
B.
Tyr
chosen
Tyr is a Norse god associated primarily with law, justice, and heroic courage, famously known for sacrificing his hand to the wolf Fenrir.
-
C.
Tyr
Tyr is a rural settlement located within the Nikolaevsky District of Khabarovsk Krai in Russia.
-
D.
Týr
Týr is a Norse god associated with law, justice, and heroic glory, best known for sacrificing his hand to bind the monstrous wolf Fenrir.
-
E.
Bilskirnir
Bilskirnir is the immense, many-roomed hall of the thunder god Thor in Norse mythology, located in the region of Þrúðvangar.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff13523f548190beafd130f8741465 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:19 a.m.