Triple
T13815385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kärpät Oulu |
E332001
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Oulun Kärpät |
E332001
|
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: Oulun Kärpät | Statement: [Kärpät Oulu, formerName, Oulun Kärpät]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oulun Kärpät Context triple: [Kärpät Oulu, formerName, Oulun Kärpät]
-
A.
Kärpät Oulu
chosen
Kärpät Oulu is a prominent Finnish professional ice hockey club from Oulu, known as one of the most successful teams in the Liiga.
-
B.
Oulun Kiekko
Oulun Kiekko is an ice hockey club from Oulu, Finland, known locally as a rival to the prominent Kärpät Oulu team.
-
C.
Jokerit
Jokerit is a professional ice hockey club from Helsinki, Finland, known as one of the country’s most successful and popular teams.
-
D.
HIFK Helsinki
HIFK Helsinki is a prominent professional ice hockey club from Helsinki, Finland, known as one of the country’s most successful and traditional teams in the Liiga.
-
E.
Porin Ässät
Porin Ässät is a Finnish professional ice hockey club based in the city of Pori, competing in the country’s top-tier Liiga.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c70454a8819097b5e5091f84be33 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:12 p.m.