Triple
T19460913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meet the Robinsons |
E486864
|
entity |
| Predicate | animationTechnology |
P136011
|
FINISHED |
| Object | computer 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: computer animation | Statement: [Meet the Robinsons, animationTechnology, computer animation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animationTechnology Context triple: [Meet the Robinsons, animationTechnology, computer animation]
-
A.
animationSoftware
Indicates that an entity is a software application used to create, edit, or render animations for another entity (such as a project, asset, or user).
-
B.
animationStudio
Indicates that one entity is an animation studio responsible for creating, producing, or animating the other entity.
-
C.
animator
Indicates that one entity serves as the animator or creator of animated content for another entity or work.
-
D.
animationDirector
Indicates that one entity serves as the animation director responsible for overseeing and guiding the animation work of another entity.
-
E.
featuresAnimation
Indicates that something includes or prominently presents an animation as part of its content or functionality.
- F. None of above. chosen
Provenance (4 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c983f481908b2684dc4380b889 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.