Triple
T23725336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National 5 |
E586257
|
entity |
| Predicate | canBeTakenBy |
P146733
|
FINISHED |
| Object | older learners in further education colleges |
—
|
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: older learners in further education colleges | Statement: [National 5, canBeTakenBy, older learners in further education colleges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTakenBy Context triple: [National 5, canBeTakenBy, older learners in further education colleges]
-
A.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
B.
canBeTakenQuickly
Indicates that the action or resource can be obtained, completed, or utilized in a short amount of time.
-
C.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
-
D.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
E.
mayTake
chosen
Indicates that an entity is permitted or allowed to take, enroll in, or participate in another entity (such as a course, resource, or opportunity).
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b914adc08190b339c7f83f1536d7 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:08 p.m.