Triple
T14376879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tórshavn |
E356497
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Norse god Thor |
E199352
|
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: Norse god Thor | Statement: [Tórshavn, namedAfter, Norse god Thor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Norse god Thor Context triple: [Tórshavn, namedAfter, Norse god Thor]
-
A.
Norse god Thor
chosen
Norse god Thor is a hammer-wielding deity of thunder, storms, and strength from Norse mythology, renowned as a protector of gods and humans.
-
B.
Odin
Odin is the chief god in Norse mythology, associated with wisdom, war, poetry, and magic, and revered as the ruler of Asgard and the Aesir gods.
-
C.
Þórr
Þórr is the Norse god of thunder, storms, and protection, famed for wielding the hammer Mjölnir and defending gods and humans from giants.
-
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.
Tôr
Tôr is a small village in the municipality of Loulé in Portugal’s Algarve region, known for its rural character and surrounding vineyards.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900949fc81909be0da1734c46645 |
completed | April 14, 2026, 7:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c5728fc819089ef3c7c34b10101 |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:16 a.m.