Triple
T21690402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albany campus |
E535345
|
entity |
| Predicate | hasStudentLifeComponent |
P33631
|
FINISHED |
| Object | student 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: student services | Statement: [Albany campus, hasStudentLifeComponent, student services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentLifeComponent Context triple: [Albany campus, hasStudentLifeComponent, student services]
-
A.
hasStudentServices
chosen
Indicates that an entity provides or is associated with student support services for another entity or group.
-
B.
hasStudentSection
Indicates that an entity (such as a course or class) is associated with a specific student section or subgroup of enrolled students.
-
C.
hasStudentBodyFrom
Indicates that an educational institution draws or enrolls its student body from a specified geographic area, group, or source.
-
D.
studentComponent
Indicates that one entity functions as a student-related part, module, or subunit within a larger system, structure, or context.
-
E.
hasStudentOrganization
Indicates that an entity (such as an institution or department) is associated with or hosts a particular student organization.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cfaab08190b400e1538afc8c43 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.