Triple
T17627903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downpayment Plus Program |
E429895
|
entity |
| Predicate | hasFinancialForm |
P128328
|
FINISHED |
| Object | grant assistance |
—
|
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: grant assistance | Statement: [Downpayment Plus Program, hasFinancialForm, grant assistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinancialForm Context triple: [Downpayment Plus Program, hasFinancialForm, grant assistance]
-
A.
hasFinancialStatements
Indicates that an entity possesses or is associated with one or more formal financial statements documenting its financial performance or position.
-
B.
hasQuarterlyReportForm
Indicates that an entity is associated with or required to use a specific form for submitting quarterly reports.
-
C.
hadBusinessForm
Indicates that an entity possessed or utilized a particular business form or organizational structure in the context of its activities or operations.
-
D.
hasAnnualReportForm
Indicates that an entity is associated with a specific form used for its annual report.
-
E.
hasCashForm
Indicates that something exists or is available specifically in the form of cash.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbe3a308190a818d04f1a9b15f7 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:52 a.m.