Triple
T24602042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Goose Records |
E608851
|
entity |
| Predicate | reissueFocus |
P83235
|
FINISHED |
| Object | classic blues recordings |
—
|
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: classic blues recordings | Statement: [Blue Goose Records, reissueFocus, classic blues recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reissueFocus Context triple: [Blue Goose Records, reissueFocus, classic blues recordings]
-
A.
reauthorizationFocus
Indicates a focus on renewing, extending, or updating an existing authorization or approval.
-
B.
importFocus
Indicates that attention, priority, or emphasis is being brought into or concentrated on a particular entity or aspect.
-
C.
focusIssue
Indicates that an issue, topic, or problem is the primary subject of attention or concern in a given context.
-
D.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
-
E.
reissueFeature
chosen
Indicates that an existing item (such as a product, document, or media release) is being issued again, typically with updates, changes, or in a new edition or format.
- 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.