Triple
T33339056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greensleeves Records |
E853618
|
entity |
| Predicate | hasCatalogueSeries |
P148473
|
FINISHED |
| Object | Greensleeves Rhythm Album series |
—
|
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: Greensleeves Rhythm Album series | Statement: [Greensleeves Records, hasCatalogueSeries, Greensleeves Rhythm Album series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogueSeries Context triple: [Greensleeves Records, hasCatalogueSeries, Greensleeves Rhythm Album series]
-
A.
associatedCatalogSeries
chosen
Indicates that one entity is linked to a catalog series with which it is grouped, classified, or otherwise contextually connected.
-
B.
hasProminentSeries
Indicates that an entity is notably associated with a major or well-known series as a defining feature.
-
C.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
D.
hasSeriesSubject
Indicates that a series is about, centers on, or thematically focuses on a particular subject.
-
E.
hasPublicationSeries
Indicates that an entity is part of, or associated with, a particular publication series.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 1, 2026, 1:34 a.m.