Triple

T24078077
Position Surface form Disambiguated ID Type / Status
Subject Runaround Sue E596431 entity
Predicate usesSongForm P97672 FINISHED
Object verse-chorus form 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: verse-chorus form | Statement: [Runaround Sue, usesSongForm, verse-chorus form]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesSongForm
Context triple: [Runaround Sue, usesSongForm, verse-chorus form]
  • A. songForm chosen
    Indicates the structural pattern or arrangement of sections that defines how a song is organized.
  • B. isForSong
    Indicates that something is intended to be used with, associated with, or applicable to a particular song.
  • C. musicContribution
    Indicates that an entity has contributed in some way to the creation, performance, or production of a musical work.
  • D. isSongIn
    Indicates that a particular song is contained within or belongs to a specified collection, such as an album, playlist, or soundtrack.
  • E. featuresSongwriter
    Indicates that a musical work includes or credits a particular person as its songwriter.
  • 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_69e288c3999c8190809b282a04813dec completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1db1f4c98819089a0e470593baf5b completed April 29, 2026, 10:19 a.m.
PD Predicate disambiguation batch_69f1764b1d4c8190b12590c6339c31c1 completed April 29, 2026, 3:08 a.m.
Created at: April 17, 2026, 10:43 p.m.