Triple
T15090747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glaðsheimr |
E360406
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ásgarðr |
E72584
|
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: Ásgarðr | Statement: [Glaðsheimr, locatedIn, Ásgarðr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ásgarðr Context triple: [Glaðsheimr, locatedIn, Ásgarðr]
-
A.
Asgard
chosen
Asgard is the celestial stronghold of the Norse gods, especially the Aesir, often depicted as a fortified realm connected to the human world by the rainbow bridge Bifröst.
-
B.
Alfheim
Alfheim is the luminous realm of the light elves in Norse mythology, often associated with beauty, fertility, and the god Freyr.
-
C.
Vanaheim
Vanaheim is the mythological home of the Vanir, a tribe of fertility and nature gods in Norse mythology.
-
D.
Miðgarðr
Miðgarðr is the human-inhabited world in Norse mythology, situated at the center of the cosmos and encircled by a vast ocean.
-
E.
Glaðsheimr
Glaðsheimr is a hall or region in Norse mythology where the chief gods, including Odin, gather for council within the divine realm.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00277ea808190be3f002a8316eff1 |
completed | April 15, 2026, 9:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae1d7a0c819096b035f8ca8d0e90 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:04 a.m.