Triple
T28994960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster (song) |
E736127
|
entity |
| Predicate | isBSide |
P164685
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Monster (song), isBSide, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBSide Context triple: [Monster (song), isBSide, no]
-
A.
isBSideOf
Indicates that one entity is located on the B side or secondary face of another entity, typically in a two-sided or dual-orientation context.
-
B.
hasBside
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.
-
C.
hasBsideStatus
chosen
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).
-
D.
isBsideTrack
Indicates that one track is the B-side counterpart associated with another primary (A-side) track, typically on a single release.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side of 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7fe920819086c9eafc065bbf11 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:30 a.m.