Triple
T36341335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Worry Song |
E894928
|
entity |
| Predicate | animatedPerformer |
P103828
|
FINISHED |
| Object | Jerry Mouse |
—
|
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: Jerry Mouse | Statement: [The Worry Song, animatedPerformer, Jerry Mouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animatedPerformer Context triple: [The Worry Song, animatedPerformer, Jerry Mouse]
-
A.
animatedCharacter
chosen
Indicates that an entity is a fictional character depicted through animation rather than live action.
-
B.
animator
Indicates that one entity serves as the animator or creator of animated content for another entity or work.
-
C.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
D.
animationStudio
Indicates that one entity is an animation studio responsible for creating, producing, or animating the other entity.
-
E.
motionCapturePerformer
Indicates a relationship where a performer provides motion data, typically through sensors or tracking, to drive the movement of a digital character or animation.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.