Triple
T23828622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sun Is Shining |
E589452
|
entity |
| Predicate | isBsideTrack |
P153773
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Sun Is Shining, isBsideTrack, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBsideTrack Context triple: [The Sun Is Shining, isBsideTrack, true]
-
A.
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.
-
B.
originalReleaseAsBsideOf
Indicates that a work was first released as the B-side of another primary release (such as a single or main track).
-
C.
isDoubleAlbumTrack
Indicates that a track belongs to an album that was released as a double album (i.e., spanning two discs or equivalent units).
-
D.
isTitleTrackOfSide
Indicates that a track serves as the title track for a specific side of a multi-sided release (e.g., side A or side B).
-
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. chosen
Provenance (4 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f304f08190bd965df06f013b3f |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8 p.m.