Triple
T8273830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grove School of Engineering |
E193490
|
entity |
| Predicate | servesStudentBodyType |
P5246
|
FINISHED |
| Object | diverse |
—
|
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: diverse | Statement: [Grove School of Engineering, servesStudentBodyType, diverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesStudentBodyType Context triple: [Grove School of Engineering, servesStudentBodyType, diverse]
-
A.
hasStudentBodyType
chosen
Indicates that an educational institution possesses a student body characterized by a particular type or classification.
-
B.
hasStudentBodyFrom
Indicates that an educational institution draws or enrolls its student body from a specified geographic area, group, or source.
-
C.
representsStudentBody
Indicates that one entity serves as the official representative or governing body for the students of another entity (such as a school or institution).
-
D.
hasStudentServices
Indicates that an entity provides or is associated with student support services for another entity or group.
-
E.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798a13388190a3610766d265a61f |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:50 p.m.