Triple

T9928949
Position Surface form Disambiguated ID Type / Status
Subject Harald zur Hausen E192594 entity
Predicate givenName P17 FINISHED
Object Harald E153143 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: Harald | Statement: [Harald zur Hausen, givenName, Harald]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harald
Context triple: [Harald zur Hausen, givenName, Harald]
  • A. Harald chosen
    Harald is a common Scandinavian male given name, historically borne by several notable kings and figures in Norse and European history.
  • B. Olav Haraldsson
    Olav Haraldsson, better known as Saint Olaf, was the early 11th-century king of Norway whose efforts to consolidate Christianity led to his canonization and status as Norway’s patron saint.
  • C. Harold Bluetooth
    Harold Bluetooth was a 10th-century king of Denmark and Norway known for uniting much of Scandinavia and for inspiring the name of the modern Bluetooth wireless technology standard.
  • D. 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.
  • E. Haakon
    Haakon is a Scandinavian male given name of Old Norse origin, traditionally borne by Norwegian kings and other notable figures.
  • 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_69ca82dd978c8190947124ab0d3315ac completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb5b215c481909e0bca43f158bd82 completed April 2, 2026, 12:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20e258e888190ae4e2abac80e3399 completed April 5, 2026, 7:24 a.m.
Created at: March 30, 2026, 8:43 p.m.