Triple
T3077833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrold |
E64179
|
entity |
| Predicate | hasRelatedName |
P3889
|
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: [Harrold, hasRelatedName, Harald]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harald Context triple: [Harrold, hasRelatedName, 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.
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.
-
C.
Haakon
Haakon is a Scandinavian male given name of Old Norse origin, traditionally borne by Norwegian kings and other notable figures.
-
D.
Gorm the Old
Gorm the Old was a 10th-century king of Denmark, traditionally regarded as the first historically recognized Danish monarch and the founder of the Danish royal dynasty.
-
E.
Haakon Magnus
Haakon Magnus is the Crown Prince of Norway and heir apparent to the Norwegian throne.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a6f6148190ae5cd6e45eda9006 |
completed | March 8, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b24b21a2548190a04d122494f8c247 |
completed | March 12, 2026, 5:12 a.m. |
Created at: March 8, 2026, 3:02 p.m.