Triple
T8945199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnley College |
E213203
|
entity |
| Predicate | providesQualification |
P78552
|
FINISHED |
| Object | A-level |
—
|
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: A-level | Statement: [Burnley College, providesQualification, A-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesQualification Context triple: [Burnley College, providesQualification, A-level]
-
A.
providedQualificationFor
Indicates that one entity supplied or granted a qualification, credential, or certification that another entity possesses or uses.
-
B.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
C.
offersQualificationType
chosen
Indicates that an entity provides or makes available a specific type or category of qualification.
-
D.
currentQualificationIncludes
Indicates that an entity’s present qualification set contains or encompasses a specified qualification or component.
-
E.
qualifiesFrom
Indicates that one entity gains an official status, capability, or eligibility as a result of successfully completing or meeting the requirements of 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66db998c8190999a7a686bbdda1f |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.