Triple
T30897558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bustin' Out |
E787067
|
entity |
| Predicate | reissueStatus |
P166326
|
FINISHED |
| Object | reissued on CD |
—
|
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: reissued on CD | Statement: [Bustin' Out, reissueStatus, reissued on CD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reissueStatus Context triple: [Bustin' Out, reissueStatus, reissued on CD]
-
A.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
B.
reReleaseStatus
chosen
Indicates the release state or condition of something in relation to a prior or original release.
-
C.
reissueFeature
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.
-
D.
reissuePolicy
Indicates the rules or conditions under which an existing item (such as a ticket, document, or policy) may be reissued or replaced.
-
E.
reissueIncludes
Indicates that a reissued version of something contains or incorporates the referenced item as part of that reissue.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923c906c81908450147ba40dfeec |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.