Triple
T17989181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lethbridge College |
E430321
|
entity |
| Predicate | academicCredential |
P122287
|
FINISHED |
| Object | certificates |
—
|
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: certificates | Statement: [Lethbridge College, academicCredential, certificates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicCredential Context triple: [Lethbridge College, academicCredential, certificates]
-
A.
academicDegree
Indicates that an entity holds or has been awarded a specific academic degree.
-
B.
hasEducationalAchievement
chosen
Indicates that an entity has attained a specific level, degree, or form of formal educational accomplishment.
-
C.
eligibleDegree
Indicates that an academic degree qualifies its holder to be considered eligible for a particular program, position, or requirement.
-
D.
academicStatus
Indicates the educational or scholarly standing or level an entity holds within an academic context.
-
E.
educationType
Indicates the specific category or level of education associated with an entity, such as formal, informal, primary, secondary, or higher education.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29e47a88190be58b79c73d3e652 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.