Triple

T17610833
Position Surface form Disambiguated ID Type / Status
Subject Career-related Programme E428959 entity
Predicate supportsPathwaysTo P29720 FINISHED
Object universities 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: universities | Statement: [Career-related Programme, supportsPathwaysTo, universities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsPathwaysTo
Context triple: [Career-related Programme, supportsPathwaysTo, universities]
  • A. supportsPathway
    Indicates that one entity contributes to, enables, or maintains the functioning or progression of a specified pathway.
  • B. hasPathway
    Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
  • C. offersPathway chosen
    Indicates that one entity provides a route, means, or opportunity for another entity to reach, access, or transition to something.
  • D. supportsReach
    Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
  • E. acceptsCareerPath
    Indicates that one entity approves or agrees to follow a proposed career path associated with another entity.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46d2d294881908380b2ab0b4d2503 completed April 19, 2026, 5:50 a.m.
PD Predicate disambiguation batch_69e3cdd7da34819099bc9481c5a79bab completed April 18, 2026, 6:30 p.m.
Created at: April 10, 2026, 5:51 a.m.