Triple
T12203855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Ain’t Alone |
E290784
|
entity |
| Predicate | showcasesBandSensibilities |
P104302
|
FINISHED |
| Object | blues-rock sensibilities |
—
|
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: blues-rock sensibilities | Statement: [You Ain’t Alone, showcasesBandSensibilities, blues-rock sensibilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showcasesBandSensibilities Context triple: [You Ain’t Alone, showcasesBandSensibilities, blues-rock sensibilities]
-
A.
observesBand
Indicates that one entity watches, studies, or monitors a musical band.
-
B.
sensitivityFeature
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
-
C.
supportedBands
Indicates that one entity (typically a musician or band) performed as a supporting or opening act for another band.
-
D.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other entity.
-
E.
providesSensoryEffects
Indicates that one entity causes or contributes to sensory experiences or perceptions in another entity.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d938ca32908190bd56f563efcbe8a0 |
completed | April 10, 2026, 5:52 p.m. |
Created at: April 8, 2026, 9:51 p.m.