Triple

T7852637
Position Surface form Disambiguated ID Type / Status
Subject Haakon V of Norway E182093 entity
Predicate givenName P17 FINISHED
Object Haakon 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: Haakon | Statement: [Haakon V of Norway, givenName, Haakon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Haakon
Context triple: [Haakon V of Norway, givenName, Haakon]
  • A. Haakon chosen
    Haakon is a Scandinavian male given name of Old Norse origin, traditionally borne by Norwegian kings and other notable figures.
  • B. 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.
  • 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 the Good
    Haakon the Good was a 10th-century king of Norway known for his attempts to strengthen royal power and introduce Christianity to his traditionally pagan 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_69ca82869ee08190b8f9040dbc2c0467 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb18ec48548190960bd564a60effa8 completed March 31, 2026, 12:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5b161a4881909641f3a29c1650b4 completed March 31, 2026, 5:26 a.m.
Created at: March 30, 2026, 4:51 p.m.