Triple
T19241730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dollar Academy |
E481148
|
entity |
| Predicate | hasExaminations |
P86246
|
FINISHED |
| Object | Scottish Qualifications Authority exams |
—
|
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: Scottish Qualifications Authority exams | Statement: [Dollar Academy, hasExaminations, Scottish Qualifications Authority exams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExaminations Context triple: [Dollar Academy, hasExaminations, Scottish Qualifications Authority exams]
-
A.
hasExaminationBranch
Indicates that an entity is associated with or conducted through a specific examination branch or division.
-
B.
examinedIn
Indicates that one entity is analyzed, inspected, or studied within the context, scope, or setting provided by another entity.
-
C.
hasExercises
Indicates that something includes, provides, or is associated with one or more exercises.
-
D.
hasCheckInProcedure
Indicates that there is a defined process or set of steps required for an entity to check in or be checked in.
-
E.
offersExaminations
chosen
Indicates that one entity provides or makes available examinations or tests to 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf2353c819094a9a1af3a858715 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.