Triple
T5138494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SaiPa |
E115885
|
entity |
| Predicate | hasRival |
P1375
|
FINISHED |
| Object | 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: Kärpät | Statement: [SaiPa, hasRival, Kärpät]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kärpät Context triple: [SaiPa, hasRival, 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.
Jokerit
Jokerit is a professional ice hockey club from Helsinki, Finland, known as one of the country’s most successful and popular teams.
-
C.
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.
-
D.
Ilves
Ilves is a prominent Finnish sports club from Tampere best known for its ice hockey team competing in the country’s top professional league.
-
E.
FC Honka
FC Honka is a Finnish professional football club based in Espoo that competes in the country’s top-tier league.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd787acd18819087f09db885893c3e |
completed | March 20, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bec4d342c8819088f67c01d3769a6d |
completed | March 21, 2026, 4:18 p.m. |
Created at: March 20, 2026, 1:43 p.m.