Triple
T36455700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middlesex University Dubai |
E898144
|
entity |
| Predicate | studentServices |
P33631
|
FINISHED |
| Object | careers support |
—
|
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: careers support | Statement: [Middlesex University Dubai, studentServices, careers support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentServices Context triple: [Middlesex University Dubai, studentServices, careers support]
-
A.
studentSupport
Indicates that one entity provides academic, emotional, or practical assistance to another in an educational context.
-
B.
hasStudentServices
chosen
Indicates that an entity provides or is associated with student support services for another entity or group.
-
C.
studentComponent
Indicates that one entity functions as a student-related part, module, or subunit within a larger system, structure, or context.
-
D.
studentsWing
Indicates a relationship where a particular wing, section, or area is designated for or associated with students.
-
E.
targetStudentService
Indicates a relationship where a particular student is the intended recipient or focus of a specific service or support action.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.