Triple
T29245673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silenzio, Bruno! |
E741434
|
entity |
| Predicate | spokenByVoiceActorOfCharacter |
P115423
|
FINISHED |
| Object | Jack Dylan Grazer |
—
|
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: Jack Dylan Grazer | Statement: [Silenzio, Bruno!, spokenByVoiceActorOfCharacter, Jack Dylan Grazer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenByVoiceActorOfCharacter Context triple: [Silenzio, Bruno!, spokenByVoiceActorOfCharacter, Jack Dylan Grazer]
-
A.
spokenBy
Indicates that a particular utterance, statement, or piece of speech is produced or said by a specific entity.
-
B.
voiceActorOfPerformer
chosen
Indicates that one performer provides the voice for a character or role portrayed by another performer.
-
C.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
D.
currentlySpokenBy
Indicates that a language is presently being used as a spoken language by a person or group.
-
E.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66489459c8190aa343cb2b8af1300 |
completed | May 2, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:32 p.m.