Triple
T13801064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SM-sarja |
E331639
|
entity |
| Predicate | notableClub |
P8182
|
FINISHED |
| Object | Lukko |
E887553
|
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: Lukko | Statement: [SM-sarja, notableClub, Lukko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lukko Context triple: [SM-sarja, notableClub, Lukko]
-
A.
Lukko Rauma
chosen
Lukko Rauma is a Finnish professional ice hockey club from Rauma that competes in the country’s top league, Liiga.
-
B.
Lokki
Lokki is the highest mountain peak on the Faroe Islands island of Borðoy.
-
C.
Lutakko
Lutakko is a central lakeside district of Jyväskylä, Finland, known for its modern residential areas, event venues, and the annual Jyväskylä Rock Festival.
-
D.
Lakki
Lakki is a coastal town and main port on the Greek island of Leros in the Dodecanese.
-
E.
Liski
Liski is a town in southwestern Russia that serves as an important railway junction and administrative center within Voronezh Oblast.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ded6c8190851c108ae559a355 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b0893a20819081d4001b8dbc9c36 |
completed | May 3, 2026, 8:31 p.m. |
Created at: April 9, 2026, 10:11 p.m.