Triple

T18762243
Position Surface form Disambiguated ID Type / Status
Subject Jonsson E458798 entity
Predicate hasSurname P18 FINISHED
Object Jonsson 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: Jonsson | Statement: [Jonsson, hasSurname, Jonsson]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jonsson
Context triple: [Jonsson, hasSurname, Jonsson]
  • A. Jonsson chosen
    Jonsson is the namesake of the Jonsson-Rowland Science Center, likely a significant benefactor or figure associated with the institution that houses it.
  • B. Johnsson
    Johnsson is a Scandinavian surname, most commonly found in Sweden, that is a patronymic variant of the name Johnson.
  • C. Johannsson
    Johannsson is a character in August Strindberg’s expressionist play "The Ghost Sonata," contributing to its eerie, dreamlike exploration of guilt and illusion.
  • D. Williamsson
    Williamsson is a Scandinavian patronymic surname, likely meaning "son of William" and used as a variant of the more common form Williamson.
  • E. Danielsson
    Danielsson is a Swedish surname commonly borne by individuals of Scandinavian origin.
  • 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e58d7fd5008190823bc7e37fdd6669 completed April 20, 2026, 2:20 a.m.
Created at: April 10, 2026, 11:52 a.m.