Triple
T15393698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thrúd |
E368113
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Magni |
E250346
|
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: Magni | Statement: [Thrúd, relative, Magni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Magni Context triple: [Thrúd, relative, Magni]
-
A.
Magni
chosen
Magni is a Norse god, one of Thor’s sons, renowned in mythology for his immense strength and survival of Ragnarök.
-
B.
Hoderi
Hoderi is a deity in Japanese mythology, known as the elder son of Ninigi-no-Mikoto and an ancestor of seafaring clans.
-
C.
Helvius
Helvius is an ancient Roman family name (nomen) associated with members of the Helvia gens, such as the physician Helvius Successus.
-
D.
Forseti
Forseti is the Norse god of justice and reconciliation, renowned for his wisdom and skill in mediating disputes among gods and men.
-
E.
Magno
Magno is an American rapper from Houston, Texas, known for his work in the Southern hip hop scene and collaborations with the Swishahouse collective.
- 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_69ff1350699c8190acf7830d88455851 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:19 a.m.