Triple
T817484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sierra National Forest |
E17680
|
entity |
| Predicate | hasFireRegime |
P20871
|
FINISHED |
| Object | frequent wildfires |
—
|
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: frequent wildfires | Statement: [Sierra National Forest, hasFireRegime, frequent wildfires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFireRegime Context triple: [Sierra National Forest, hasFireRegime, frequent wildfires]
-
A.
hasFireHistory
Indicates that an entity has experienced one or more fire events in the past.
-
B.
hasMajorForest
Indicates that an entity possesses or contains a large, significant forested area.
-
C.
hasNationalForest
Indicates that a place or jurisdiction contains, includes, or is home to at least one designated national forest.
-
D.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
E.
fireJurisdiction
Indicates that one entity has official authority and responsibility over fire protection, prevention, or response activities within the area or domain of another entity.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:38 p.m.