Triple

T33305875
Position Surface form Disambiguated ID Type / Status
Subject I Can't Do the Sum E852726 entity
Predicate hasFictionalCharacterSinger P62476 FINISHED
Object Mary Contrary NE NERFINISHED

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: Mary Contrary | Statement: [I Can't Do the Sum, hasFictionalCharacterSinger, Mary Contrary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalCharacterSinger
Context triple: [I Can't Do the Sum, hasFictionalCharacterSinger, Mary Contrary]
  • A. hasFictionalPerformer chosen
    Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
  • B. hasFictionalSong
    Indicates that one entity includes, features, or is associated with a song that is fictional or exists only within a narrative context.
  • C. hasFictionalSpeaker
    Indicates that a work, text, or expression is presented as being spoken by an invented or non-real speaker rather than an actual person.
  • D. hasFictionalLeadCharacter
    Indicates that a creative work features a particular fictional character as its main or leading protagonist.
  • E. isFictionalPersonFrom
    Indicates that a fictional person originates from or is associated with a particular place or source.
  • 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_69f349679fd8819093b9b40e989440e3 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ff14d596e88190be5263b7f96a96cd completed May 9, 2026, 11:04 a.m.
PD Predicate disambiguation batch_69ff13f0208081909369aeb3b77a6b1f completed May 9, 2026, 11:01 a.m.
Created at: May 1, 2026, 1:33 a.m.