Triple
T16845064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Semaphore Version of Wuthering Heights |
E409514
|
entity |
| Predicate | parodiesForm |
P10352
|
FINISHED |
| Object | serious literary adaptation |
—
|
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: serious literary adaptation | Statement: [The Semaphore Version of Wuthering Heights, parodiesForm, serious literary adaptation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parodiesForm Context triple: [The Semaphore Version of Wuthering Heights, parodiesForm, serious literary adaptation]
-
A.
parodies
chosen
Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
-
B.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
C.
usedForHumor
Indicates that something is employed with the intention of being funny, amusing, or comical.
-
D.
hasHumorousTreatmentOf
Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
-
E.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3541a008190b2a97cfea92b170f |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.