Triple
T23887460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retro Active |
E600372
|
entity |
| Predicate | containsBsideFromSingleBy |
P15273
|
FINISHED |
| Object | Def Leppard |
—
|
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: Def Leppard | Statement: [Retro Active, containsBsideFromSingleBy, Def Leppard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBsideFromSingleBy Context triple: [Retro Active, containsBsideFromSingleBy, Def Leppard]
-
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.
singleAorBside
Indicates that exactly one of the two related entities is on side A or side B, but not both simultaneously.
-
D.
originalReleaseAsBsideOf
Indicates that a work was first released as the B-side of another primary release (such as a single or main track).
-
E.
onAlbumSide
Indicates that a particular track or song appears on a specified side (e.g., Side A or Side B) of an album.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cd00dc8c8190af641147b2efff3e |
completed | April 29, 2026, 9:18 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.