Triple
T246391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cleveland Show |
E5046
|
entity |
| Predicate | animationStyle |
P1851
|
FINISHED |
| Object | 2D digital 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: 2D digital animation | Statement: [The Cleveland Show, animationStyle, 2D digital animation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animationStyle Context triple: [The Cleveland Show, animationStyle, 2D digital animation]
-
A.
animationStudio
Indicates that one entity is an animation studio responsible for creating, producing, or animating the other entity.
-
B.
artisticStyle
chosen
Indicates the artistic movement, style, or aesthetic approach that characterizes how something is created or visually expressed.
-
C.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
D.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
E.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d13b8088190a3f48f0388d57496 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.