Triple

T1110810
Position Surface form Disambiguated ID Type / Status
Subject Musaf E25591 entity
Predicate notRecitedOn P24459 FINISHED
Object regular weekdays 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: regular weekdays | Statement: [Musaf, notRecitedOn, regular weekdays]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notRecitedOn
Context triple: [Musaf, notRecitedOn, regular weekdays]
  • A. notObservedIn
    Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
  • B. notAwardedIn
    Indicates that a particular award or recognition was not given to an entity within a specified context, such as a year, event, or category.
  • C. hasNotableRecordingBy
    Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
  • D. spokenBefore
    Indicates that one entity has spoken or produced speech earlier in time than another entity.
  • E. notRecognizedBy
    Indicates that one entity does not acknowledge, accept, or formally recognize the status, authority, or validity of another entity.
  • 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_69a49428d4448190b3b36991ceae87ce completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bbd92a8c8190a16e55f3f739010f completed March 1, 2026, 10:21 p.m.
PD Predicate disambiguation batch_69a4bb42990c819080db96478fd4977e completed March 1, 2026, 10:18 p.m.
PDg Predicate description generation batch_69a4bbd7ff1881908c943ecdfea59e81 completed March 1, 2026, 10:21 p.m.
Created at: March 1, 2026, 7:43 p.m.