Triple
T7958823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxnard College |
E184807
|
entity |
| Predicate | hasStudentSupportService |
P33631
|
FINISHED |
| Object | counseling services |
—
|
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: counseling services | Statement: [Oxnard College, hasStudentSupportService, counseling services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentSupportService Context triple: [Oxnard College, hasStudentSupportService, counseling services]
-
A.
hasStudentServices
chosen
Indicates that an entity provides or is associated with student support services for another entity or group.
-
B.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasEducationalSupportFrom
Indicates that one entity receives educational assistance, guidance, or resources from another entity.
-
D.
hasStudentSection
Indicates that an entity (such as a course or class) is associated with a specific student section or subgroup of enrolled students.
-
E.
hasEducationServices
Indicates that one entity provides or offers educational services to another entity or within a particular context.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b80050c81909b2db95ade495052 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:11 p.m.