Triple
T26580508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Construction Grants Program under the Clean Water Act |
E667064
|
entity |
| Predicate | fundingTarget |
P36498
|
FINISHED |
| Object | municipalities |
—
|
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: municipalities | Statement: [Construction Grants Program under the Clean Water Act, fundingTarget, municipalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingTarget Context triple: [Construction Grants Program under the Clean Water Act, fundingTarget, municipalities]
-
A.
raisedMoneyFor
Indicates that one entity collected or obtained funds specifically to support or benefit another entity, cause, or purpose.
-
B.
fundingObjective
chosen
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
-
C.
fundingCommitment
Indicates a promise or obligation by one party to provide a specified amount or type of funding to another party or project.
-
D.
crowdfundingGoalMet
Indicates that the funding target for a crowdfunding campaign has been reached or exceeded.
-
E.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:02 a.m.