Triple
T25198449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyro 2: Ripto's Rage! |
E631063
|
entity |
| Predicate | voiceActorForSpyro |
P158016
|
FINISHED |
| Object | Tom Kenny |
—
|
NE NERFINISHED |
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: Tom Kenny | Statement: [Spyro 2: Ripto's Rage!, voiceActorForSpyro, Tom Kenny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceActorForSpyro Context triple: [Spyro 2: Ripto's Rage!, voiceActorForSpyro, Tom Kenny]
-
A.
voiceActorOfSpiderHam
Indicates that one entity serves as the voice actor for the character Spider-Ham in a performance or production.
-
B.
voiceActorForMario
Indicates that one entity serves as the voice actor who provides the spoken or vocal performance for the character Mario in a work or series of works.
-
C.
voiceActorOfPerformer
Indicates that one performer provides the voice for a character or role portrayed by another performer.
-
D.
voiceActorOfTom
Indicates that one entity serves as the voice actor for the character or role associated with Tom.
-
E.
voiceActorOfMonster
Indicates that one entity provides the voice acting performance for a monster character in a work.
- F. None of above. chosen
Provenance (4 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b409808190b41f2edafc801130 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:50 p.m.