Triple
T8593339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jansson |
E203483
|
entity |
| Predicate | derivesFromGivenName |
P3325
|
FINISHED |
| Object | Johan |
E567797
|
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: Johan | Statement: [Jansson, derivesFromGivenName, Johan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Johan Context triple: [Jansson, derivesFromGivenName, Johan]
-
A.
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.
-
B.
Johan
Johan is the given first name of the Swedish playwright and novelist August Strindberg.
-
C.
Johan
chosen
Johan is a masculine given name of Scandinavian origin, commonly used in countries such as Norway, Sweden, and Denmark.
-
D.
Johanus
Johanus is a given name, likely a variant or diminutive of Johan, used as a personal first name in some cultures.
-
E.
Johann
Johann is a given name of Germanic origin commonly used in German-speaking and other European countries.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4668b49481908838579e9876c1ec |
completed | March 31, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea8becbd88190837478e302d5e5b4 |
completed | April 2, 2026, 5:34 p.m. |
Created at: March 30, 2026, 6:23 p.m.