Triple
T16832470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Response Teams |
E409183
|
entity |
| Predicate | deploymentTrigger |
P110288
|
FINISHED |
| Object | regional disaster declaration |
—
|
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: regional disaster declaration | Statement: [Regional Response Teams, deploymentTrigger, regional disaster declaration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentTrigger Context triple: [Regional Response Teams, deploymentTrigger, regional disaster declaration]
-
A.
deploymentSource
Indicates the origin or mechanism from which something is deployed, such as the system, process, or source responsible for initiating the deployment.
-
B.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
C.
deploymentBody
Indicates that something serves as the physical or textual body/content of a deployment.
-
D.
deploymentCondition
chosen
Indicates the specific requirements or circumstances under which something may be deployed or put into operation.
-
E.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b318b8b88190b3266f4f06a955c1 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.