Triple
T7914363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haakon |
E183781
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Håkon |
E183781
|
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: Håkon | Statement: [Haakon, hasVariant, Håkon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Håkon Context triple: [Haakon, hasVariant, Håkon]
-
A.
Håkon
Håkon is one of the official mascots of the 1994 Winter Olympics held in Lillehammer, Norway, depicted as a Norwegian child symbolizing the country’s heritage and Olympic spirit.
-
B.
Haakon
chosen
Haakon is a Scandinavian male given name of Old Norse origin, traditionally borne by Norwegian kings and other notable figures.
-
C.
Haakon Magnus
Haakon Magnus is the Crown Prince of Norway and heir apparent to the Norwegian throne.
-
D.
Haakon the Young
Haakon the Young was a 13th-century Norwegian prince and co-king, known as the eldest surviving son and designated heir of King Haakon IV of Norway.
-
E.
Haakon V
Haakon V was a medieval King of Norway, notable as the last ruler of the House of Sverre and for moving the Norwegian capital to Oslo.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a759b548190af2e2aa0705d7051 |
completed | March 31, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbde69b608190a49d93c04c46787d |
completed | April 1, 2026, 6:40 a.m. |
Created at: March 30, 2026, 5:04 p.m.