Triple

T35291500
Position Surface form Disambiguated ID Type / Status
Subject Technikon Witwatersrand E1019238 entity
Predicate offeredProgrammes P69363 FINISHED
Object engineering 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: engineering | Statement: [Technikon Witwatersrand, offeredProgrammes, engineering]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offeredProgrammes
Context triple: [Technikon Witwatersrand, offeredProgrammes, engineering]
  • A. offeredProgrammeType
    Indicates the type or category of programme that is being offered by an entity.
  • B. programOffered chosen
    Indicates that a particular program is made available or provided by a given entity (such as an institution, organization, or provider).
  • C. offersProfessionalPrograms
    Indicates that an entity provides formal, career-oriented educational or training programs to others.
  • D. offersProgramsThrough
    Indicates that one entity provides or delivers its programs, services, or courses by means of, or via the infrastructure or platform of, another entity.
  • E. offersProgramsAt
    Indicates that an organization or institution provides or runs specific programs at a particular location or facility.
  • 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_69f76de7eedc8190a3bdc64ebbc05b42 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fe6739d4dc8190ae7505c089bbac29 completed May 8, 2026, 10:44 p.m.
PD Predicate disambiguation batch_69fe6541dffc81909c66a61ba69f38fc completed May 8, 2026, 10:35 p.m.
Created at: May 3, 2026, 4:03 p.m.