Triple
T31850166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spinnin' Deep |
E813043
|
entity |
| Predicate | hasReleasesType |
—
|
GENERATED |
| Object | singles |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleasesType Context triple: [Spinnin' Deep, hasReleasesType, singles]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
-
C.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
-
D.
hasReleaseModel
chosen
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
E.
hasReleaseBranch
Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
- F. None of above.
Provenance (1 batch)
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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:51 p.m.