Triple
T1562785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson |
E33363
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Jonsen |
E177563
|
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: Jonsen | Statement: [Johnson, hasSpellingVariant, Jonsen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jonsen Context triple: [Johnson, hasSpellingVariant, Jonsen]
-
A.
Johnsen
chosen
Johnsen is a surname of Scandinavian origin, commonly used as a patronymic family name meaning "son of John."
-
B.
Jens
Jens is a masculine given name commonly used in Scandinavian and German-speaking countries, equivalent to "John" in English.
-
C.
Martinsen
Martinsen is a Scandinavian patronymic surname meaning "son of Martin," related to the Spanish surname Martinez.
-
D.
Nilsen
Nilsen is a surname, primarily of Scandinavian origin, that serves as a variant spelling of Nelson.
-
E.
Robertsen
Robertsen is a surname of likely Scandinavian origin, functioning as a patronymic variant of the name Roberts.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a908886efc8190a630ef1e06d0d9cb |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad40217be88190ae17abcf1541ec55 |
completed | March 8, 2026, 9:23 a.m. |
Created at: March 4, 2026, 7:27 p.m.