Triple
T11357217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasper |
E268987
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Kasper |
E593969
|
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: Kasper | Statement: [Jasper, hasVariant, Kasper]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kasper Context triple: [Jasper, hasVariant, Kasper]
-
A.
Kasper
Kasper is a surname most notably associated with former American football wide receiver Kevin Kasper.
-
B.
Jesper
chosen
Jesper is a masculine given name commonly used in Scandinavian countries and parts of Europe.
-
C.
Caspar
Caspar is one of the Three Wise Men in Christian tradition, often depicted as a king who visited the infant Jesus bearing gifts.
-
D.
Johan
Johan is the given first name of J. Erik Jonsson, an American businessman and philanthropist who co-founded Texas Instruments and served as mayor of Dallas.
-
E.
Johan
Johan is a masculine given name of Scandinavian origin, commonly used in countries such as Norway, Sweden, and Denmark.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea419afc8190b3a93141d015ebdf |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58b8d5f5c8190a80a52f2063bb5b0 |
completed | April 20, 2026, 2:12 a.m. |
Created at: April 8, 2026, 9:33 p.m.