Triple
T14376852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National 5 Gaelic qualifications |
E356496
|
entity |
| Predicate | frameworkLevel |
P113801
|
FINISHED |
| Object | SCQF level 5 |
—
|
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: SCQF level 5 | Statement: [National 5 Gaelic qualifications, frameworkLevel, SCQF level 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameworkLevel Context triple: [National 5 Gaelic qualifications, frameworkLevel, SCQF level 5]
-
A.
frameworkLayer
Indicates a relationship where one framework is organized within, built upon, or conceptually assigned to a particular architectural or conceptual layer.
-
B.
frameworkSupport
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by another entity.
-
C.
frameworkName
Indicates that a specific framework is identified by the given name.
-
D.
frameworkPresented
Indicates that a particular framework has been formally introduced or shown to an audience or recipient.
-
E.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900949fc81909be0da1734c46645 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.