Triple
T29338611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Disaster Response Fund |
E743976
|
entity |
| Predicate | disbursalCriteria |
P1130
|
FINISHED |
| Object | severity of disaster |
—
|
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: severity of disaster | Statement: [National Disaster Response Fund, disbursalCriteria, severity of disaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disbursalCriteria Context triple: [National Disaster Response Fund, disbursalCriteria, severity of disaster]
-
A.
disburses
Indicates the act of paying out or distributing funds or resources from a source to a recipient.
-
B.
disbursementOption
Indicates the method or arrangement by which funds are paid out or distributed.
-
C.
grantingCriteria
Indicates the conditions or requirements that must be satisfied for something (such as a request, permission, or benefit) to be granted.
-
D.
beneficiaryRequirement
Indicates that one entity has a requirement specifying who or what must be the beneficiary of a particular action, service, or resource.
-
E.
eligibilityCriteria
chosen
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f669255db48190a9541c77cb9b5ede |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:32 p.m.