Triple
T4867494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Minus Zero/No Limit |
E109006
|
entity |
| Predicate | sideOnOriginalLP |
P25310
|
FINISHED |
| Object | Side 1 |
—
|
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: Side 1 | Statement: [Love Minus Zero/No Limit, sideOnOriginalLP, Side 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOnOriginalLP Context triple: [Love Minus Zero/No Limit, sideOnOriginalLP, Side 1]
-
A.
sideOnVinylSingle
Indicates that a musical track appears on a specific side (A or B) of a vinyl single record.
-
B.
onAlbumSide
chosen
Indicates that a particular track or song appears on a specified side (e.g., Side A or Side B) of an album.
-
C.
A-sideWith
Indicates that one entity is aligned or positioned on the same side as another entity.
-
D.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
-
E.
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.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7bb0b88190bbc24498619910fc |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.