Triple

T12679328
Position Surface form Disambiguated ID Type / Status
Subject ePGP (online postgraduate programme) E302903 entity
Predicate scheduleDesign P73352 FINISHED
Object designed to accommodate working hours 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: designed to accommodate working hours | Statement: [ePGP (online postgraduate programme), scheduleDesign, designed to accommodate working hours]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scheduleDesign
Context triple: [ePGP (online postgraduate programme), scheduleDesign, designed to accommodate working hours]
  • A. schedule
    Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
  • B. scheduleUS
    Indicates that an entity arranges or assigns a time for something specifically within the context of the United States.
  • C. scheduledDuring
    Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
  • D. scheduleUsage chosen
    Indicates how and when a schedule is applied or utilized in relation to associated entities or events.
  • E. scheduledAs
    Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a 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_69d7bdee64a08190801c6d470aefd723 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d961b1dff48190923290555ece5d89 completed April 10, 2026, 8:46 p.m.
PD Predicate disambiguation batch_69d960bb64ec8190bd0400cf0cc8b0a7 completed April 10, 2026, 8:42 p.m.
Created at: April 9, 2026, 5:21 p.m.