Triple

T22029996
Position Surface form Disambiguated ID Type / Status
Subject "Tomorrow, and tomorrow, and tomorrow" E544058 entity
Predicate repetitionDevice P46166 FINISHED
Object anaphora 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: anaphora | Statement: ["Tomorrow, and tomorrow, and tomorrow", repetitionDevice, anaphora]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: repetitionDevice
Context triple: ["Tomorrow, and tomorrow, and tomorrow", repetitionDevice, anaphora]
  • A. repetitionOf
    Indicates that one entity is a repeated occurrence or instance of another entity, preserving the same content or pattern.
  • B. usesRepetition
    Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
  • C. repetitionRole
    Indicates that one entity serves a specific function or role within a repeated or recurring occurrence of another entity or event.
  • D. causesRepetitionOf
    Indicates that one entity brings about or is responsible for the recurrence or repeated occurrence of another entity or event.
  • E. lyricDevice chosen
    Indicates a relationship where a lyrical technique or stylistic device is employed within or by a piece of text, such as a song or poem.
  • 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_69e11e2f98c8819083e11eab90942a78 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127ed0cb08190aead0838cc62934c completed April 28, 2026, 9:34 p.m.
PD Predicate disambiguation batch_69e6f63b0d048190b241622759aab9de completed April 21, 2026, 3:59 a.m.
Created at: April 16, 2026, 8:24 p.m.