Triple
T28147871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sketch Show |
E714531
|
entity |
| Predicate | hasNotableSketchStyle |
P49092
|
FINISHED |
| Object | Short, punchy sketches |
—
|
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: Short, punchy sketches | Statement: [The Sketch Show, hasNotableSketchStyle, Short, punchy sketches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSketchStyle Context triple: [The Sketch Show, hasNotableSketchStyle, Short, punchy sketches]
-
A.
hasNotableSketch
Indicates that an entity is associated with a sketch that is considered notable or significant in some context.
-
B.
sketchType
chosen
Indicates the specific kind or category of sketch associated with an entity or action.
-
C.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
D.
hasSculptureStyle
Indicates that a sculpture is created in, or associated with, a particular artistic style or sculptural tradition.
-
E.
hasStyleCharacteristics
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: April 27, 2026, 9:57 p.m.