Triple
T20196702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimpshrine recordings |
E493102
|
entity |
| Predicate | includesReleaseType |
P3286
|
FINISHED |
| Object | EP |
—
|
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: EP | Statement: [Crimpshrine recordings, includesReleaseType, EP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesReleaseType Context triple: [Crimpshrine recordings, includesReleaseType, EP]
-
A.
releasesInclude
Indicates that a particular release or distribution contains, bundles, or makes available the specified component, item, or content.
-
B.
appliesToReleaseType
Indicates that a rule, condition, or attribute is specifically relevant or restricted to a particular type of release.
-
C.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
D.
supportsReleasesOf
Indicates that one entity provides assistance, resources, or endorsement for the publication or rollout of another entity’s releases.
-
E.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad99d50819090ddb7b546c65321 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.