Triple
T33044312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business and Technology Education Council |
E845551
|
entity |
| Predicate | targetLearnerGroup |
P11007
|
FINISHED |
| Object | post-16 learners |
—
|
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: post-16 learners | Statement: [Business and Technology Education Council, targetLearnerGroup, post-16 learners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetLearnerGroup Context triple: [Business and Technology Education Council, targetLearnerGroup, post-16 learners]
-
A.
targetStudentGroup
chosen
Indicates a relationship where something is directed, tailored, or intended specifically for a particular group of students.
-
B.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
C.
targetStudentsFrom
Indicates that an entity directs its efforts, services, or offerings specifically toward a defined group of students.
-
D.
laterTrainingGroup
Indicates that one training group occurs chronologically after another training group.
-
E.
targetStudentService
Indicates a relationship where a particular student is the intended recipient or focus of a specific service or support action.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 1, 2026, 1:24 a.m.