Triple

T27977763
Position Surface form Disambiguated ID Type / Status
Subject Infamy Speech E706536 entity
Predicate characterizesDateAs P103279 FINISHED
Object a date which will live in infamy 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: a date which will live in infamy | Statement: [Infamy Speech, characterizesDateAs, a date which will live in infamy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterizesDateAs
Context triple: [Infamy Speech, characterizesDateAs, a date which will live in infamy]
  • A. dateDetermination
    Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
  • B. dateDescription chosen
    Indicates a textual description or label that characterizes the nature, context, or details of a particular date or dating event between entities.
  • C. dateCategory
    Indicates the classification of a date into a specific temporal category (such as day type, period, or time-based grouping).
  • D. dateSignificance
    Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
  • E. dateOf
    Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
  • 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_69ef96b7f330819090f315318ba6977e completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f7aa699d68819081ed363931894ab3 completed May 3, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69f7a8cec6d48190bebfa884b2f938c0 completed May 3, 2026, 7:58 p.m.
Created at: April 27, 2026, 7:42 p.m.