Triple
T6169129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAFSA |
E137645
|
entity |
| Predicate | typeOfAidCovered |
P936
|
FINISHED |
| Object | need-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: need-based aid | Statement: [FAFSA, typeOfAidCovered, need-based aid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAidCovered Context triple: [FAFSA, typeOfAidCovered, need-based aid]
-
A.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
B.
awardedForCoverageType
Indicates that something (such as an award, benefit, or recognition) is granted specifically in relation to a particular type or category of coverage.
-
C.
typeOfDiscriminationCovered
Indicates that a particular kind or category of discriminatory behavior is included within the scope of protections, rules, or analysis.
-
D.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
E.
typeOfSupport
chosen
Indicates the kind or category of assistance, help, or backing provided in a given context.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d8de56481909583104c70a52616 |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:18 p.m.