Triple
T37271649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost Pines Forest |
E924528
|
entity |
| Predicate | 2011FireImpact |
P43620
|
FINISHED |
| Object | large portions of forest burned |
—
|
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: large portions of forest burned | Statement: [Lost Pines Forest, 2011FireImpact, large portions of forest burned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2011FireImpact Context triple: [Lost Pines Forest, 2011FireImpact, large portions of forest burned]
-
A.
bushfiresImpact
chosen
Indicates how bushfires affect or influence other entities, conditions, or outcomes.
-
B.
wildfireRisk
Indicates the likelihood or potential severity of wildfires occurring in a given area or under specific conditions.
-
C.
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.
-
D.
fireOccurred
Indicates that a fire event took place at a specific time and/or location.
-
E.
hasFireRegime
Indicates that an area or ecosystem is characterized by a particular pattern, frequency, and intensity of fires over time.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.