Triple
T37620128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Center complex |
E936043
|
entity |
| Predicate | hasStudentServiceUse |
P33631
|
FINISHED |
| Object | student support offices |
—
|
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 support offices | Statement: [University Center complex, hasStudentServiceUse, student support offices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudentServiceUse Context triple: [University Center complex, hasStudentServiceUse, student support offices]
-
A.
hasStudentServices
chosen
Indicates that an entity provides or is associated with student support services for another entity or group.
-
B.
hasStudentAccessTo
Indicates that a student is granted permission to access or use a particular resource, system, or location.
-
C.
hasStudentCode
Indicates that an entity is associated with a specific student identification code assigned to it.
-
D.
hasStudentEnrollment
Indicates that a person or entity is enrolled as a student in a particular course, program, or educational institution.
-
E.
hasStudentMembership
Indicates that an entity holds or is associated with a membership specifically designated for students.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0087de41c48190b2743a26b6d65409 |
completed | May 10, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_6a00870a8bc48190be1385579b8cc1dd |
completed | May 10, 2026, 1:24 p.m. |
Created at: May 3, 2026, 4:18 p.m.