Triple
T7733655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Göran Lindblad |
E175325
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Göran |
E244957
|
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: Göran | Statement: [Göran Lindblad, givenName, Göran]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Göran Context triple: [Göran Lindblad, givenName, Göran]
-
A.
Göran
chosen
Göran is a Swedish masculine given name, commonly used in Sweden and borne by various notable figures.
-
B.
Gösta
Gösta is a masculine given name of Swedish origin, notably borne by the mathematician Gösta Mittag-Leffler.
-
C.
Pehr
Pehr is a masculine given name of Scandinavian origin, notably borne by Finnish statesman P. E. Svinhufvud.
-
D.
Olof
Olof is a Scandinavian male given name, particularly common in Sweden and Norway, derived from Old Norse and borne by various notable historical and cultural figures.
-
E.
Ingvar
Ingvar is a Scandinavian given name of Old Norse origin, historically associated with Viking-age figures and meaning roughly "Ing’s warrior" or "warrior of the god Ing."
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70339c4b481909a56ae13f501e794 |
completed | March 27, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8be355e04819088598b5c7d61b848 |
completed | March 29, 2026, 5:52 a.m. |
Created at: March 27, 2026, 4:06 p.m.