Triple
T9712031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish folklore |
E235042
|
entity |
| Predicate | coreFigure |
P74551
|
FINISHED |
| Object | Tapio |
E255454
|
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: Tapio | Statement: [Finnish folklore, coreFigure, Tapio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tapio Context triple: [Finnish folklore, coreFigure, Tapio]
-
A.
Tapio
chosen
Tapio is a Finnish masculine given name commonly associated with figures in Finnish culture, design, and mythology.
-
B.
Tapio Wirkkala
Tapio Wirkkala was a renowned Finnish designer and sculptor celebrated for his influential work in glass, industrial design, and modern Finnish aesthetics.
-
C.
Paavo
Paavo is a Finnish masculine given name most famously borne by legendary distance runner Paavo Nurmi.
-
D.
Erkki
Erkki is a Finnish masculine given name commonly used as a variant of names like Eero or Erik.
-
E.
Paavo Lonkila
Paavo Lonkila was a Finnish cross-country skier who won multiple Olympic and World Championship medals in the early 1950s.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0705f8819095852263009c28c5 |
completed | April 1, 2026, 10:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f8c26dc8190a6fa21bde27ba6fa |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:19 p.m.