Triple
T32036084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Morris (voice) |
E818097
|
entity |
| Predicate | hasGivenVoiceToCharacterIn |
P161313
|
FINISHED |
| Object | Pixar film |
—
|
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: Pixar film | Statement: [John Morris (voice), hasGivenVoiceToCharacterIn, Pixar film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenVoiceToCharacterIn Context triple: [John Morris (voice), hasGivenVoiceToCharacterIn, Pixar film]
-
A.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
-
B.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
C.
voiceCharacter
chosen
Indicates that one entity provides the voice for, or vocally portrays, a particular character in a work.
-
D.
hasWrittenDialogueFor
Indicates that one entity has created or authored dialogue content for another entity, such as a work, project, or production.
-
E.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49b23448190a6c600187b66c7c7 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:18 a.m.