Triple
T11728159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karlssen |
E278828
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Karlson |
E278822
|
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: Karlson | Statement: [Karlssen, hasSpellingVariant, Karlson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Karlson Context triple: [Karlssen, hasSpellingVariant, Karlson]
-
A.
Karlsson
chosen
Karlsson is a Scandinavian variant of the surname Carlson, commonly found in Sweden and other Nordic countries.
-
B.
Karl Karlsson
Karl Karlsson is the birth name of Charles XI, who was King of Sweden from 1660 to 1697 and a key consolidator of royal power in the Swedish Empire.
-
C.
Herman Beeftink
Herman Beeftink is a Dutch-born composer and musician known for his work on film and television scores, including the 2018 adaptation of "Fahrenheit 451."
-
D.
Milo
Milo is a small town located in Yates County in the Finger Lakes region of New York State.
-
E.
Milo
Milo is a masculine given name commonly used as a short or affectionate form of longer names such as Emilio.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f16679c0ec81909fe80d75dd582db1 |
completed | April 29, 2026, 2:01 a.m. |
Created at: April 8, 2026, 9:41 p.m.