Triple

T23807144
Position Surface form Disambiguated ID Type / Status
Subject pre-1962 Roman Missal E589738 entity
Predicate calendarIncludes P126215 FINISHED
Object many pre-20th-century saints 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: many pre-20th-century saints | Statement: [pre-1962 Roman Missal, calendarIncludes, many pre-20th-century saints]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: calendarIncludes
Context triple: [pre-1962 Roman Missal, calendarIncludes, many pre-20th-century saints]
  • A. calendarFeature
    Indicates that an entity provides or supports calendar-related functionality, such as scheduling, event management, or date-based organization.
  • B. calendarContribution
    Indicates a relationship where an entity adds to, modifies, or otherwise participates in the creation or maintenance of a calendar or scheduled events.
  • C. calendarVariesBy
    Indicates that the characteristics or values of a calendar (such as dates, events, or structure) change depending on another specified factor or context.
  • D. calendarAssociation chosen
    Indicates a relationship where one entity is linked to or associated with a particular calendar or calendaring context (such as events, schedules, or timeframes).
  • E. calendarDependence
    Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
  • 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_69e25d19fecc8190a5cf39bbb18d5d7f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c752ff6481908cfc20d4f178d526 completed April 29, 2026, 8:54 a.m.
PD Predicate disambiguation batch_69f155fe300481909bd617443228df65 completed April 29, 2026, 12:51 a.m.
Created at: April 17, 2026, 7:56 p.m.