Triple
T23605780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolting Rhymes |
E582891
|
entity |
| Predicate | hasAdaptationFormat |
P1690
|
FINISHED |
| Object | television special |
—
|
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: television special | Statement: [Revolting Rhymes, hasAdaptationFormat, television special]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptationFormat Context triple: [Revolting Rhymes, hasAdaptationFormat, television special]
-
A.
hasAdaptationStrategy
Indicates that an entity employs or is associated with a specific method or approach for adapting to changing conditions or requirements.
-
B.
hasMediaAdaptation
chosen
Indicates that a work has been adapted into another medium, such as film, television, or other forms of media.
-
C.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
D.
hasAdaptationRoleIn
Indicates that an entity serves a specific adaptation-related role or function within another entity, process, or context.
-
E.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0ef32b481909590a1a5853df5d9 |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:44 p.m.