Triple
T16426450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stretch Records |
E398954
|
entity |
| Predicate | releasesInclude |
P122739
|
FINISHED |
| Object | solo piano albums |
—
|
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: solo piano albums | Statement: [Stretch Records, releasesInclude, solo piano albums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasesInclude Context triple: [Stretch Records, releasesInclude, solo piano albums]
-
A.
releases
Indicates that one entity causes something to be set free, emitted, or made available from its control or containment.
-
B.
reissueIncludes
Indicates that a reissued version of something contains or incorporates the referenced item as part of that reissue.
-
C.
supportsReleasesOf
Indicates that one entity provides assistance, resources, or endorsement for the publication or rollout of another entity’s releases.
-
D.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
E.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fb6cd881908fb6cd1c60f5ac3c |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.