Triple
T28441854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monkeybone |
E715731
|
entity |
| Predicate | liveActionAnimationBlend |
P127988
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Monkeybone, liveActionAnimationBlend, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveActionAnimationBlend Context triple: [Monkeybone, liveActionAnimationBlend, yes]
-
A.
mixesLiveActionAndAnimation
chosen
Indicates that the work combines live-action footage with animated elements within the same production.
-
B.
liveAction
Indicates that an entity is a live-action (non-animated) adaptation, portrayal, or version of another entity.
-
C.
isAnimatedBy
Indicates that an entity’s motion or behavior is driven, controlled, or brought to life by another entity or process.
-
D.
animationTechnology
Indicates a relationship where one entity uses, is created with, or is characterized by a particular animation technology.
-
E.
liveActionModelFor
Indicates that one entity serves as the live-action (real-world filmed) representation or counterpart of another entity, typically an animated or non-live-action version.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e3da3908190a38f80a9fe4cadba |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:46 a.m.