Triple

T24784461
Position Surface form Disambiguated ID Type / Status
Subject Sourcery E620080 entity
Predicate containsParodyOf P10352 FINISHED
Object traditional high fantasy tropes 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 high fantasy tropes | Statement: [Sourcery, containsParodyOf, traditional high fantasy tropes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: containsParodyOf
Context triple: [Sourcery, containsParodyOf, traditional high fantasy tropes]
  • A. parodies chosen
    Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
  • B. conflictsWithParodies
    Indicates that one entity is in conflict with another entity specifically in the context of parody, such as opposing, contradicting, or undermining the other through parody.
  • C. originalHitPerformerParodied
    Indicates that the subject is the original performer of a hit work that is being parodied by the object.
  • D. isComedySongBy
    Indicates that a song belongs to the comedy genre and is performed or created by a specified artist or group.
  • E. originalSongwriterParodied
    Indicates that one entity is the songwriter of an original song that is parodied by 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_69e2fabdbe8c8190adbb9434b8636cad completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f65aa07c048190a5df30d53d8f0cf5 completed May 2, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69f659cc571c819097e51e531961d812 completed May 2, 2026, 8:08 p.m.
Created at: April 18, 2026, 4:45 a.m.