Triple
T27738768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockin’ Chair |
E697592
|
entity |
| Predicate | hasSingleA-Side |
P171376
|
FINISHED |
| Object | Roll With It |
—
|
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: Roll With It | Statement: [Rockin’ Chair, hasSingleA-Side, Roll With It]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleA-Side Context triple: [Rockin’ Chair, hasSingleA-Side, Roll With It]
-
A.
hasNotableA-Side
Indicates that an item (typically a single or record) is associated with a specific notable A-side track.
-
B.
singleAorBside
Indicates that exactly one of the two related entities is on side A or side B, but not both simultaneously.
-
C.
pairedWithA-side
chosen
Indicates that one entity is paired or matched with another entity designated as the A-side in a two-sided or dual configuration.
-
D.
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.
-
E.
A-sideWith
Indicates that one entity is aligned or positioned on the same side as 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 3:13 p.m.