Triple
T30444768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Ana winds |
E774545
|
entity |
| Predicate | effectOnWildfires |
P158214
|
FINISHED |
| Object | increase wildfire spread |
—
|
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: increase wildfire spread | Statement: [Santa Ana winds, effectOnWildfires, increase wildfire spread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnWildfires Context triple: [Santa Ana winds, effectOnWildfires, increase wildfire spread]
-
A.
wildfireRisk
Indicates the likelihood or potential severity of wildfires occurring in a given area or under specific conditions.
-
B.
wildfireRiskDriver
chosen
Indicates a factor or condition that contributes to or influences the level of wildfire risk.
-
C.
methodOfKillingWildfire
Indicates the method or technique used to kill or extinguish a wildfire.
-
D.
bushfiresImpact
Indicates how bushfires affect or influence other entities, conditions, or outcomes.
-
E.
fireEcologyRole
Indicates the role or function an entity has in ecological processes related to fire, such as how it influences, responds to, or depends on fire within an ecosystem.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 8:08 p.m.