Triple
T6393288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johan Henrik Nebelong |
E143879
|
entity |
| Predicate | givenName |
P17
|
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: [Johan Henrik Nebelong, givenName, Johan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Johan Context triple: [Johan Henrik Nebelong, givenName, 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0687f5c6c81909c835329c996b311 |
completed | March 22, 2026, 10:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6388f42648190adbc2d1c1efa75a5 |
completed | March 27, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:34 p.m.