Triple
T9498198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pehr Evind Svinhufvud |
E229066
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Svinhufvud |
E229066
|
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: Svinhufvud | Statement: [Pehr Evind Svinhufvud, familyName, Svinhufvud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Svinhufvud Context triple: [Pehr Evind Svinhufvud, familyName, Svinhufvud]
-
A.
Svinhufvud
chosen
Svinhufvud is a notable Finnish surname most prominently associated with Pehr Evind Svinhufvud, a key statesman and third President of Finland.
-
B.
Jóhan
Jóhan is a given name, primarily used in Faroese and other Nordic contexts, that corresponds to the name Johan.
-
C.
Ólafur
Ólafur is an Icelandic given name, equivalent to the Old Norse name Óláfr and commonly borne by men in Iceland.
-
D.
Jóhann
Jóhann is an Icelandic male given name commonly borne by figures in the arts, sports, and public life.
-
E.
Haraldur
Haraldur is an Icelandic given name, equivalent to Harald, commonly used for males in Iceland.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95ef06b88190b7a840caddea3e38 |
completed | April 1, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12d3aafb88190ac53289039bca88a |
completed | April 4, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:56 p.m.