Triple
T22686256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of Sciences and Mathematics |
E560922
|
entity |
| Predicate | possibleDegreeLevel |
P149244
|
FINISHED |
| Object | graduate programs |
—
|
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: graduate programs | Statement: [College of Sciences and Mathematics, possibleDegreeLevel, graduate programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleDegreeLevel Context triple: [College of Sciences and Mathematics, possibleDegreeLevel, graduate programs]
-
A.
eligibleDegree
Indicates that an academic degree qualifies its holder to be considered eligible for a particular program, position, or requirement.
-
B.
hasDegree
Indicates that an entity possesses or has been awarded a specific academic or professional degree.
-
C.
hasHighestDegree
Indicates that one entity possesses the highest academic degree attained by another entity.
-
D.
academicDegree
Indicates that an entity holds or has been awarded a specific academic degree.
-
E.
typicalDegree
Indicates the usual or characteristic level, intensity, or extent to which something holds or applies in a given context.
- F. None of above. chosen
Provenance (4 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178637bc08190a8dfb33b5f4249e5 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:12 p.m.