Triple
T25336974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California’s State Responsibility Area wildlands |
E635302
|
entity |
| Predicate | includesFireHazardSeverityZoneCategory |
P60801
|
FINISHED |
| Object | Moderate |
—
|
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: Moderate | Statement: [California’s State Responsibility Area wildlands, includesFireHazardSeverityZoneCategory, Moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFireHazardSeverityZoneCategory Context triple: [California’s State Responsibility Area wildlands, includesFireHazardSeverityZoneCategory, Moderate]
-
A.
floodRiskCategory
Indicates the level or classification of flood risk associated with an entity, such as a location or asset.
-
B.
hazardLevelSystem
Indicates a system’s assigned degree of risk or danger within a defined hazard classification framework.
-
C.
hasHazardLevel
chosen
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
D.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
E.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 21, 2026, 1:32 p.m.