Triple
T25702684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamela |
E644506
|
entity |
| Predicate | parodiesAuthor |
P10352
|
FINISHED |
| Object | Samuel Richardson |
—
|
NE NERFINISHED |
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: Samuel Richardson | Statement: [Shamela, parodiesAuthor, Samuel Richardson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parodiesAuthor Context triple: [Shamela, parodiesAuthor, Samuel Richardson]
-
A.
parodies
chosen
Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
-
B.
originalSongwriterParodied
Indicates that one entity is the songwriter of an original song that is parodied by another entity.
-
C.
originalHitPerformerParodied
Indicates that the subject is the original performer of a hit work that is being parodied by the object.
-
D.
hasHumorousTreatmentOf
Indicates that one entity presents or portrays another entity in a humorous, comedic, or joking manner.
-
E.
alliedWithParodies
Indicates that one entity forms an alliance or cooperative association with another entity specifically in the context of creating, supporting, or engaging in parodies.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc0e881081909ac33b3e42e82471 |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 8:49 p.m.