Triple

T26828707
Position Surface form Disambiguated ID Type / Status
Subject Miss Prism E675437 entity
Predicate backstoryEventDetail P148591 FINISHED
Object confused a baby with a manuscript and placed the baby in a handbag 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: confused a baby with a manuscript and placed the baby in a handbag | Statement: [Miss Prism, backstoryEventDetail, confused a baby with a manuscript and placed the baby in a handbag]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: backstoryEventDetail
Context triple: [Miss Prism, backstoryEventDetail, confused a baby with a manuscript and placed the baby in a handbag]
  • A. notableEventResponse
    Indicates a response, reaction, or consequence that occurs as a result of a notable event.
  • B. hasHistoricalEvent
    Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
  • C. notableStoryEvent chosen
    Indicates that an event plays a significant or memorable role within the narrative or storyline associated with the subject.
  • D. expandsBackstoryOf
    Indicates that one entity provides additional background details or context that elaborate on the history or origins of another entity.
  • E. knowledgeOfPastEvents
    Indicates that an entity is aware of or has information about events that occurred in the past.
  • 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_69eee9b776448190993a60b67fcc9545 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61adb3c348190ac6b1744ee520276 completed May 2, 2026, 3:40 p.m.
PD Predicate disambiguation batch_69f611ad2eb48190ac1ed0090f13f7a9 completed May 2, 2026, 3:01 p.m.
Created at: April 27, 2026, 5 a.m.