Triple
T6490056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Records |
E148011
|
entity |
| Predicate | reissueActivity |
P51852
|
FINISHED |
| Object | Beatles catalog reissues in CD era |
—
|
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: Beatles catalog reissues in CD era | Statement: [Apple Records, reissueActivity, Beatles catalog reissues in CD era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reissueActivity Context triple: [Apple Records, reissueActivity, Beatles catalog reissues in CD era]
-
A.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
B.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
C.
canBeReissued
Indicates that something is eligible to be issued again, such as a document, license, or item that can be re-granted or re-produced after its initial issuance.
-
D.
hasReissueProgram
chosen
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
-
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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a9926fc81909db0f390e385e97d |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:52 p.m.