Triple

T18023587
Position Surface form Disambiguated ID Type / Status
Subject Young Team E431188 entity
Predicate hasSubsequentReissue P129495 FINISHED
Object remastered and reissued editions 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: remastered and reissued editions | Statement: [Young Team, hasSubsequentReissue, remastered and reissued editions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSubsequentReissue
Context triple: [Young Team, hasSubsequentReissue, remastered and reissued editions]
  • A. hasReissueProgram
    Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
  • B. hasReissuePeriod
    Indicates the time span during which something (such as a document, license, or product) may be reissued or renewed.
  • 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. previouslyIssued
    Indicates that something was issued or released at an earlier time prior to the current reference point.
  • E. wasReissued
    Indicates that an item, such as a document or edition, has been issued again after its original release.
  • F. None of above. chosen

Provenance (4 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_69d8b9050fb48190890155145deb0a66 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b9c475dc819086c4cd86d663791f completed April 19, 2026, 11:17 a.m.
PD Predicate disambiguation batch_69e3f904b8048190add43883cd7cb191 completed April 18, 2026, 9:35 p.m.
PDg Predicate description generation batch_69e42d8eefa88190a700c7c1b4213e46 completed April 19, 2026, 1:19 a.m.
Created at: April 10, 2026, 10:24 a.m.