Triple
T26898595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Johnson |
E677960
|
entity |
| Predicate | fictionalCharacterVoiced |
P13156
|
FINISHED |
| Object | Goofy |
—
|
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: Goofy | Statement: [George Johnson, fictionalCharacterVoiced, Goofy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalCharacterVoiced Context triple: [George Johnson, fictionalCharacterVoiced, Goofy]
-
A.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
B.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
C.
notableCharacterVoiced
chosen
Indicates that a notable character is voiced or performed by a specific voice actor or performer.
-
D.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
-
E.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 5:49 a.m.