Triple
T14376829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National 5 Gaelic qualifications |
E356496
|
entity |
| Predicate | typicalLearnerAge |
P78532
|
FINISHED |
| Object | 15–16 |
—
|
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: 15–16 | Statement: [National 5 Gaelic qualifications, typicalLearnerAge, 15–16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLearnerAge Context triple: [National 5 Gaelic qualifications, typicalLearnerAge, 15–16]
-
A.
typicalAge
chosen
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
B.
typicalAgeAtCompletion
Indicates the age at which an entity (such as a program, activity, or process) is typically completed.
-
C.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
approximateStartAge
Indicates the estimated or roughly determined age at which an event, condition, or state begins.
- 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_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. |
Created at: April 10, 2026, 1:16 a.m.