Triple

T8892774
Position Surface form Disambiguated ID Type / Status
Subject Concert by the Sea E211718 entity
Predicate reissueIncludes P85581 FINISHED
Object complete concert recording 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: complete concert recording | Statement: [Concert by the Sea, reissueIncludes, complete concert recording]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reissueIncludes
Context triple: [Concert by the Sea, reissueIncludes, complete concert recording]
  • A. 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.
  • B. wasReissued
    Indicates that an item, such as a document or edition, has been issued again after its original release.
  • 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. reRelease
    Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
  • E. hasReissueProgram
    Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
  • 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_69ca83907954819096d52a245b635841 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61bb46c881909e579bb1926e5204 completed April 1, 2026, 12:07 a.m.
PD Predicate disambiguation batch_69cc5c2aec04819093c932fe51c0f08d completed March 31, 2026, 11:43 p.m.
PDg Predicate description generation batch_69cc5d6e54808190af4156edd4c8ffbc completed March 31, 2026, 11:49 p.m.
Created at: March 30, 2026, 6:54 p.m.