Triple
T9674600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School Improvement Grants |
E234115
|
entity |
| Predicate | fundingDuration |
P49263
|
FINISHED |
| Object | multi-year 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: multi-year grants | Statement: [School Improvement Grants, fundingDuration, multi-year grants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingDuration Context triple: [School Improvement Grants, fundingDuration, multi-year grants]
-
A.
fundingPeriod
chosen
Indicates the time span or duration for which funding is allocated, active, or valid within a financial or grant-related relationship.
-
B.
timeHorizonOfLoans
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
C.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
D.
fundingSpeed
Indicates how quickly financial resources are provided or disbursed within a given funding relationship or process.
-
E.
fundingModel
Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6d6dd48190a77c486337a58cb6 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.