Triple
T17435974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh My Darling, Clementine |
E424002
|
entity |
| Predicate | hasParodyVersions |
P10352
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Oh My Darling, Clementine, hasParodyVersions, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParodyVersions Context triple: [Oh My Darling, Clementine, hasParodyVersions, Yes]
-
A.
parodies
chosen
Indicates that one entity imitates another in an exaggerated or humorous way, often to criticize or comment on the original.
-
B.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
C.
hasFictionalSong
Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
-
D.
hasKaraokeVersion
Indicates that an entity has a corresponding karaoke (instrumental or sing-along) version of itself.
-
E.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4490426008190b474ed76aca5d6f3 |
completed | April 19, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.