Triple
T32381090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roxie Records |
E827418
|
entity |
| Predicate | handlesReleasesFor |
P116467
|
FINISHED |
| Object | Lenny Kravitz |
—
|
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: Lenny Kravitz | Statement: [Roxie Records, handlesReleasesFor, Lenny Kravitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesReleasesFor Context triple: [Roxie Records, handlesReleasesFor, Lenny Kravitz]
-
A.
handledReleaseOf
chosen
Indicates that one entity managed, oversaw, or was responsible for carrying out the release of another entity (such as a product, version, or document).
-
B.
supportsReleasesOf
Indicates that one entity provides assistance, resources, or endorsement for the publication or rollout of another entity’s releases.
-
C.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
-
D.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
E.
worksOnRelease
Indicates that an entity is actively involved in tasks or responsibilities related to a specific 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 12:51 a.m.