Triple
T8693719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rural Area Formula Program |
E206352
|
entity |
| Predicate | regulatesUseOfFunds |
P48625
|
FINISHED |
| Object | capital expenses |
—
|
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: capital expenses | Statement: [Rural Area Formula Program, regulatesUseOfFunds, capital expenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesUseOfFunds Context triple: [Rural Area Formula Program, regulatesUseOfFunds, capital expenses]
-
A.
fundingOversight
chosen
Indicates that one entity is responsible for monitoring, regulating, or supervising the use and allocation of funds provided to another entity.
-
B.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
C.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
D.
authorizedAppropriations
Indicates that a governing body has formally approved the allocation of funds for a specific purpose or activity.
-
E.
budgetAuthority
Indicates that an entity has the formal power or authorization to allocate, commit, or control the use of financial resources for another entity or activity.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5826bbb48190a212fb1bb06e05e6 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.