Triple

T11404884
Position Surface form Disambiguated ID Type / Status
Subject Sabina E270210 entity
Predicate breaksFourthWall P99130 FINISHED
Object true 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: true | Statement: [Sabina, breaksFourthWall, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: breaksFourthWall
Context triple: [Sabina, breaksFourthWall, true]
  • A. breaksFourthWallIn
    Indicates that an entity directly acknowledges or addresses the audience or the fact that it is in a fictional work within a given context or medium.
  • B. breaksWith
    Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
  • C. spontaneouslyBrokenBy
    Indicates that a symmetry or property is not explicitly violated by the underlying laws but is instead broken by the system’s ground state or configuration due to spontaneous symmetry breaking caused by the specified entity or mechanism.
  • D. associatedBreak
    Indicates a relationship where one entity is linked to a specific break, interruption, or pause that is relevant to its state, schedule, or operation.
  • E. break
    Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
  • F. None of above. chosen

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_69d6aaddeaa8819088b30ef7b50598c9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8014ab46881909fa1d425926c617b completed April 9, 2026, 7:43 p.m.
PD Predicate disambiguation batch_69d7e70ffd708190b62a78ebcbce9f78 completed April 9, 2026, 5:51 p.m.
PDg Predicate description generation batch_69d80010712c819089ea2e31e664abe1 completed April 9, 2026, 7:37 p.m.
Created at: April 8, 2026, 9:34 p.m.