Triple
T24391498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joshua Gomez |
E614902
|
entity |
| Predicate | performedVoiceWorkIn |
P18510
|
FINISHED |
| Object | video games industry |
—
|
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: video games industry | Statement: [Joshua Gomez, performedVoiceWorkIn, video games industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedVoiceWorkIn Context triple: [Joshua Gomez, performedVoiceWorkIn, video games industry]
-
A.
voiceWork
chosen
Indicates that one entity performs or contributes voice acting or vocal performance work for another entity or creative production.
-
B.
performedTextBy
Indicates that a text-based work (such as a script, lyrics, or written piece) is realized or executed as a performance by a specific performer or group.
-
C.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
D.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
-
E.
hasAuthorOfVoiceover
Indicates that an entity has a specific person or agent who provided the voiceover for it.
- 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2945878b481909cca6def7b64b42c |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:04 a.m.