Triple
T27027987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bright Futures |
E680841
|
entity |
| Predicate | financialAidType |
P2134
|
FINISHED |
| Object | merit-based aid |
—
|
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: merit-based aid | Statement: [Bright Futures, financialAidType, merit-based aid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialAidType Context triple: [Bright Futures, financialAidType, merit-based aid]
-
A.
scholarshipType
chosen
Indicates the specific category or kind of scholarship associated with an entity.
-
B.
hasFinancialAid
Indicates that one entity provides or is associated with financial assistance or support to another entity.
-
C.
financialAidPolicy
Indicates the rules or guidelines governing how financial assistance is determined, awarded, and managed.
-
D.
tuitionFeeType
Indicates the category or structure of tuition fees that applies to an entity (such as full-time, part-time, in-state, out-of-state, or other fee types).
-
E.
hasCommonFinancialAidPolicy
Indicates that two or more entities share the same rules, criteria, or framework governing financial aid policies.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62232f1048190be9e9467cd181055 |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:12 a.m.