Triple
T24302395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of the Canyons |
E612432
|
entity |
| Predicate | offersStudentSupportService |
P33631
|
FINISHED |
| Object | academic counseling |
—
|
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: academic counseling | Statement: [College of the Canyons, offersStudentSupportService, academic counseling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersStudentSupportService Context triple: [College of the Canyons, offersStudentSupportService, academic counseling]
-
A.
hasStudentServices
chosen
Indicates that an entity provides or is associated with student support services for another entity or group.
-
B.
studentSupport
Indicates that one entity provides academic, emotional, or practical assistance to another in an educational context.
-
C.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
D.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
E.
offersServiceTo
Indicates that one entity provides or makes a service available for the benefit or use of 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29222d3008190af765d62787ee334 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:25 a.m.