Triple
T5324192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Emergency Food Assistance Program |
E121746
|
entity |
| Predicate | fundingComponent |
P63499
|
FINISHED |
| Object | entitlement commodities |
—
|
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: entitlement commodities | Statement: [The Emergency Food Assistance Program, fundingComponent, entitlement commodities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingComponent Context triple: [The Emergency Food Assistance Program, fundingComponent, entitlement commodities]
-
A.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
B.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
C.
fundingModel
Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
-
D.
funderOf
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
E.
fundingObjective
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84561c7081909e5937c7816e492c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd86f0cbfc8190b6665dd9b28d6345 |
completed | March 20, 2026, 5:42 p.m. |
Created at: March 20, 2026, 1:59 p.m.