Triple
T21589018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonja Haraldsen |
E532729
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Haraldsen |
—
|
NE NERFINISHED |
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: Haraldsen | Statement: [Sonja Haraldsen, familyName, Haraldsen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haraldsen Context triple: [Sonja Haraldsen, familyName, Haraldsen]
-
A.
Haraldsen
chosen
Haraldsen is a Norwegian surname most notably borne by Queen Sonja of Norway before her marriage into the royal family.
-
B.
Halvard
Halvard is a masculine given name of Scandinavian origin, particularly common in Norway.
-
C.
Harald Grenske
Harald Grenske was a 10th-century Norwegian petty king of Vestfold and father of Saint Olaf II, who later became king and patron saint of Norway.
-
D.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
-
E.
Torbjørn
Torbjørn is a Scandinavian masculine given name, particularly common in Norway, derived from Old Norse elements meaning "Thor" and "bear."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefadb25108190b7a3d2e8dfc8ae60 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 16, 2026, 6:32 p.m.