Triple

T34582905
Position Surface form Disambiguated ID Type / Status
Subject Cello Concerto No. 2 E887957 entity
Predicate relativeToOtherWork P136551 FINISHED
Object follows Cello Concerto No. 1 in A minor, Op. 33 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: follows Cello Concerto No. 1 in A minor, Op. 33 | Statement: [Cello Concerto No. 2, relativeToOtherWork, follows Cello Concerto No. 1 in A minor, Op. 33]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeToOtherWork
Context triple: [Cello Concerto No. 2, relativeToOtherWork, follows Cello Concerto No. 1 in A minor, Op. 33]
  • A. workContrastedWith
    Indicates a relationship where one work is explicitly compared or set in opposition to another to highlight their differences.
  • B. hasRelationToOtherWork
    Indicates that one work bears a specified relationship (such as adaptation, sequel, reference, or influence) to another distinct work.
  • C. relatedWorkBefore chosen
    Indicates that one work is temporally or sequentially related to another work that precedes it.
  • D. relatedWorkForm
    Indicates a relationship in which one work is connected to another through a different form or version (e.g., adaptation, translation, or other format variation).
  • E. otherWork
    Indicates that one work is related to another work by the same creator, but is distinct from the primary or referenced work.
  • 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_69f349d25cbc8190869998de5915886b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_6a037c8c34f88190ace26f555827f23e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379fd7aac8190873077e63873aa72 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 2:03 a.m.