Triple
T34709178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin |
E1000589
|
entity |
| Predicate | voiceActorKnownFor |
P180080
|
FINISHED |
| Object | versatile roles in animation |
—
|
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: versatile roles in animation | Statement: [Shin, voiceActorKnownFor, versatile roles in animation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceActorKnownFor Context triple: [Shin, voiceActorKnownFor, versatile roles in animation]
-
A.
voiceActorOfPerformer
Indicates that one performer provides the voice for a character or role portrayed by another performer.
-
B.
voicedByAlsoKnownFor
chosen
Indicates that the person who voices a character is also notably recognized for another specific role or work.
-
C.
voiceActorProfession
Indicates that the subject works or is recognized professionally as a voice actor.
-
D.
notableVoiceActor
Indicates that one entity is a voice actor who is especially prominent or well-known for their work on the other entity.
-
E.
notableCharacterVoiced
Indicates that a notable character is voiced or performed by a specific voice actor or performer.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 3:59 p.m.