Triple
T9292499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Aphrodisiac Telephone |
E223553
|
entity |
| Predicate | combinesTheme |
P20708
|
FINISHED |
| Object | erotic imagery |
—
|
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: erotic imagery | Statement: [White Aphrodisiac Telephone, combinesTheme, erotic imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinesTheme Context triple: [White Aphrodisiac Telephone, combinesTheme, erotic imagery]
-
A.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
C.
themedAs
chosen
Indicates that something is characterized, styled, or organized according to a particular theme or motif.
-
D.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
E.
followsTheme
Indicates that one entity adheres to, is guided by, or is structured according to the theme established 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0866ff608190a07afac4afd0ec09 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.