Triple
T29666874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Can't Get Enough |
E750550
|
entity |
| Predicate | containsRomanticThemes |
P154818
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Can't Get Enough, containsRomanticThemes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRomanticThemes Context triple: [Can't Get Enough, containsRomanticThemes, true]
-
A.
includesRomanticCues
Indicates that the referenced content, behavior, or interaction contains elements suggestive of romantic interest, affection, or attraction between entities.
-
B.
hasRomanticPlotline
chosen
Indicates that there is a romantic storyline or relationship development present between the entities.
-
C.
romanticThemeExpressedThrough
Indicates that a romantic theme is conveyed or manifested through a particular medium, element, or aspect of a work or situation.
-
D.
hasRomanticSubplot
Indicates that a work includes a secondary storyline centered on a romantic relationship between characters.
-
E.
hasRomanticEntanglementInPlot
Indicates that a romantic relationship or involvement between characters is a significant element within the narrative plot.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 28, 2026, 7:01 p.m.