Triple
T27083774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUNY senior colleges |
E685975
|
entity |
| Predicate | alsoProvide |
P161831
|
FINISHED |
| Object | graduate education |
—
|
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 education | Statement: [CUNY senior colleges, alsoProvide, graduate education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoProvide Context triple: [CUNY senior colleges, alsoProvide, graduate education]
-
A.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
-
B.
sometimesProvides
Indicates that one entity occasionally or intermittently provides something (such as a service, resource, or support) to another entity, but not on a consistent or guaranteed basis.
-
C.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
D.
alsoIn
Indicates that an entity participates in or belongs to an additional context, group, or location alongside another already specified one.
-
E.
believedToProvide
Indicates that something is thought or assumed to offer or supply a particular benefit, effect, or resource.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6234388d08190a60ae0663a8ea9b6 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:36 a.m.