Triple
T2166950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elias Erkko |
E46930
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Helsingin Sanomat |
E72611
|
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: Helsingin Sanomat | Statement: [Elias Erkko, notableWork, Helsingin Sanomat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helsingin Sanomat Context triple: [Elias Erkko, notableWork, Helsingin Sanomat]
-
A.
Helsingin Sanomat
chosen
Helsingin Sanomat is Finland’s largest and most influential daily newspaper, widely regarded as the country’s newspaper of record.
-
B.
Ilta-Sanomat
Ilta-Sanomat is one of Finland’s largest and most influential tabloid newspapers, known for its wide circulation and popular online news portal.
-
C.
Turun Sanomat
Turun Sanomat is one of Finland’s leading regional daily newspapers, based in Turku and widely read in Southwest Finland.
-
D.
Iltalehti
Iltalehti is one of Finland’s largest and most influential tabloid newspapers, known for its wide circulation and popular online news portal.
-
E.
Aamulehti
Aamulehti is a prominent Finnish regional newspaper based in Tampere, known for its comprehensive coverage of local and national news.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeab223881908aaa2bc4f85329cc |
completed | March 7, 2026, 5:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae58f044b8819092c58022383d3468 |
completed | March 9, 2026, 5:21 a.m. |
Created at: March 4, 2026, 7:45 p.m.