Triple
T16336602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morningside Foundation |
E396693
|
entity |
| Predicate | typicalGrantType |
P10368
|
FINISHED |
| Object | large-scale institutional grants |
—
|
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: large-scale institutional grants | Statement: [Morningside Foundation, typicalGrantType, large-scale institutional grants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGrantType Context triple: [Morningside Foundation, typicalGrantType, large-scale institutional grants]
-
A.
granteeType
Indicates the classification or category of the entity that receives a grant or is granted a right, benefit, or permission.
-
B.
typeOfGrant
chosen
Indicates the specific category or kind of grant associated with an entity.
-
C.
grantType
Indicates the specific authorization or credential flow used to obtain access or permissions in a grant-based process.
-
D.
typeOfGrantManaged
Indicates that one entity manages or administers a specific type or category of grant in relation to another entity or context.
-
E.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e524448190870a6ef569017b56 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.