Triple
T36115837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalle Rovanperä |
E1044611
|
entity |
| Predicate | signedWithToyotaGazooRacingForSeason |
P83174
|
FINISHED |
| Object | 2020 |
—
|
LITERAL 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: 2020 | Statement: [Kalle Rovanperä, signedWithToyotaGazooRacingForSeason, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedWithToyotaGazooRacingForSeason Context triple: [Kalle Rovanperä, signedWithToyotaGazooRacingForSeason, 2020]
-
A.
signedWithTeam
Indicates that an entity has entered into a formal contract or agreement to join and play for a specific team.
-
B.
signedWithTeamYear
chosen
Indicates that an entity (typically a player) signed a contract with a specific team in a particular year.
-
C.
signedFromLeague
Indicates that an entity has been signed or acquired from a specified sports league.
-
D.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
E.
signedForClubFrom
Indicates that an individual joined and signed a contract with a club, having transferred from another club.
- F. None of above.
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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.