Triple
T33763387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Want Out |
E865169
|
entity |
| Predicate | hasSingleBside |
P15273
|
FINISHED |
| Object | Save Us |
—
|
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: Save Us | Statement: [I Want Out, hasSingleBside, Save Us]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleBside Context triple: [I Want Out, hasSingleBside, Save Us]
-
A.
hasBside
chosen
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
-
B.
isBsideTrack
Indicates that one track is the B-side counterpart associated with another primary (A-side) track, typically on a single release.
-
C.
originalReleaseAsBsideOf
Indicates that a work was first released as the B-side of another primary release (such as a single or main track).
-
D.
hasNotableA-Side
Indicates that an item (typically a single or record) is associated with a specific notable A-side track.
-
E.
hasBsideStatus
Indicates that one item (typically a song or track) holds the status of being the B-side counterpart to another primary item (such as an A-side single).
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 1, 2026, 1:45 a.m.