Triple
T15428073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Móðguðr |
E369564
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Gjallarbrú |
E1156208
|
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: Gjallarbrú | Statement: [Móðguðr, associatedWith, Gjallarbrú]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gjallarbrú Context triple: [Móðguðr, associatedWith, Gjallarbrú]
-
A.
Gjallarbrú
chosen
Gjallarbrú is the mythic bridge in Norse mythology that spans the river Gjöll, marking the passage into the realm of the dead, Hel.
-
B.
Gjallarhorn
Gjallarhorn is the resounding horn of the god Heimdall in Norse mythology, famously used to signal the onset of Ragnarök.
-
C.
Brísingar
Brísingar are the legendary dwarven craftsmen in Norse mythology renowned for forging the goddess Freyja’s famed necklace, Brísingamen.
-
D.
Ságat
Ságat is a Norwegian Sámi-language newspaper that serves as a key regional news source for the Sámi people.
-
E.
Straumgjerde
Straumgjerde is a village in Sykkylven Municipality in Møre og Romsdal county, Norway, known for its scenic fjord-side setting amid steep mountains.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec31f4881908b26ff7c381d7bc9 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff21a18c548190b8591776828c1793 |
completed | May 9, 2026, 11:59 a.m. |
Created at: April 10, 2026, 3:20 a.m.