Triple
T29640754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muskrat Love |
E755853
|
entity |
| Predicate | singleBside_CaptainAndTennille |
P153773
|
FINISHED |
| Object | Honey Come Love Me |
—
|
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: Honey Come Love Me | Statement: [Muskrat Love, singleBside_CaptainAndTennille, Honey Come Love Me]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleBside_CaptainAndTennille Context triple: [Muskrat Love, singleBside_CaptainAndTennille, Honey Come Love Me]
-
A.
originalReleaseAsBsideOf
Indicates that a work was first released as the B-side of another primary release (such as a single or main track).
-
B.
sideOnVinylSingle
Indicates that a musical track appears on a specific side (A or B) of a vinyl single record.
-
C.
isBsideTrack
chosen
Indicates that one track is the B-side counterpart associated with another primary (A-side) track, typically on a single release.
-
D.
singleAorBside
Indicates that exactly one of the two related entities is on side A or side B, but not both simultaneously.
-
E.
partOfMaxiSingle
Indicates that one item is a component track or element included within a maxi single 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ecece888190a653f1b981493834 |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:46 p.m.