Triple
T9039453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Step Up |
E216582
|
entity |
| Predicate | hasNotableLyricTopic |
P4921
|
FINISHED |
| Object | marital strain |
—
|
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: marital strain | Statement: [One Step Up, hasNotableLyricTopic, marital strain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLyricTopic Context triple: [One Step Up, hasNotableLyricTopic, marital strain]
-
A.
hasLyricalTheme
chosen
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
-
B.
hasLyricsTheme
Indicates that the lyrics of a work primarily concern or revolve around a specified theme or subject.
-
C.
hasSongAbout
Indicates that one entity has created, features, or is associated with a song whose subject or theme is about another entity.
-
D.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
E.
hasNotableMusicWork
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6ac46f4881909882403bb81db152 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.