Triple
T17880297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenson |
E447064
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Jensson |
—
|
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: Jensson | Statement: [Jenson, hasSpellingVariant, Jensson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jensson Context triple: [Jenson, hasSpellingVariant, Jensson]
-
A.
Jenssen
chosen
Jenssen is a Scandinavian surname, particularly common in Norway, that originated as a patronymic form meaning "son of Jens."
-
B.
Henningsen
Henningsen is a Danish surname notably associated with designer and cultural critic Poul Henningsen.
-
C.
Johnsen
Johnsen is a surname of Scandinavian origin, commonly used as a patronymic family name meaning "son of John."
-
D.
Bohlin
Bohlin is a Swedish surname associated with various notable individuals in fields such as architecture, sports, and academia.
-
E.
Jens
Jens is a small municipality in the canton of Bern in Switzerland, located within the bilingual region around the city of Biel/Bienne.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c0e56bc819097649377b520de63 |
completed | April 19, 2026, 9:10 a.m. |
Created at: April 10, 2026, 10:18 a.m.