Triple
T16795952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blame It on the Samba |
E408230
|
entity |
| Predicate | isAnimatedIn |
P114613
|
FINISHED |
| Object | traditional hand-drawn 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: traditional hand-drawn animation | Statement: [Blame It on the Samba, isAnimatedIn, traditional hand-drawn animation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAnimatedIn Context triple: [Blame It on the Samba, isAnimatedIn, traditional hand-drawn animation]
-
A.
isAnimated
Indicates that an entity possesses animation, meaning it is depicted or realized through moving images rather than static or live-action form.
-
B.
isAnimatedBy
Indicates that an entity’s motion or behavior is driven, controlled, or brought to life by another entity or process.
-
C.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
-
D.
hasAnimatedSequences
Indicates that the subject contains or includes one or more animated sequences.
-
E.
hasAnimationType
chosen
Indicates the specific style or method of animation applied to an entity or its visual content.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a96d888190a9876c3784bb7f95 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.