Triple

T28701683
Position Surface form Disambiguated ID Type / Status
Subject Play-Tone Records E729567 entity
Predicate associatedFictionalArtist P62476 FINISHED
Object The Wonders E308451 NE 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: The Wonders | Statement: [Play-Tone Records, associatedFictionalArtist, The Wonders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedFictionalArtist
Context triple: [Play-Tone Records, associatedFictionalArtist, The Wonders]
  • A. fictionalCharacterAssociatedWith
    Indicates that there is a notable connection or association between a fictional character and another entity, such as a work, creator, or universe.
  • B. hasFictionalPerformer chosen
    Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
  • C. associatedWithFictionalGroup
    Indicates that an entity has a connection or affiliation with a fictional group, organization, or collective.
  • D. hasFictionalWork
    Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
  • E. worksWithFictionalCharacter
    Indicates that one entity collaborates or interacts in a work-related context with another entity that is a fictional character.
  • F. None of above.

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_69f043e6e9688190b6bdd6e5665498ff completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_6a01b3af7b908190b4675c85d32d106c completed May 11, 2026, 10:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1ccf4e6b908190a6da3c750f82f0de completed June 1, 2026, 12:16 a.m.
PD Predicate disambiguation batch_6a01b35813c081908e484b2b9ca5dd05 completed May 11, 2026, 10:45 a.m.
Created at: April 28, 2026, 5:42 a.m.