Triple
T7547509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluebird Records |
E178442
|
entity |
| Predicate | reissueProgram |
P51852
|
FINISHED |
| Object | Bluebird reissue series |
—
|
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: Bluebird reissue series | Statement: [Bluebird Records, reissueProgram, Bluebird reissue series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reissueProgram Context triple: [Bluebird Records, reissueProgram, Bluebird reissue series]
-
A.
hasReissueProgram
chosen
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
-
B.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
C.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
D.
reauthorizesProgram
Indicates that an authority formally renews or extends the authorization for a program to continue operating.
-
E.
relaunch
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89a7b2c8190b2ca57edbb4f0390 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.