Triple
T12773715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunstan Cass |
E305313
|
entity |
| Predicate | methodOfKillingWildfire |
P106837
|
FINISHED |
| Object | reckless riding and a hunting accident |
—
|
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: reckless riding and a hunting accident | Statement: [Dunstan Cass, methodOfKillingWildfire, reckless riding and a hunting accident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfKillingWildfire Context triple: [Dunstan Cass, methodOfKillingWildfire, reckless riding and a hunting accident]
-
A.
firefightingMethods
Indicates the techniques or strategies used to control, contain, or extinguish fires.
-
B.
wildfireRisk
Indicates the likelihood or potential severity of wildfires occurring in a given area or under specific conditions.
-
C.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
D.
firefightingResponse
Indicates the action of responding to and attempting to control or extinguish a fire or related emergency.
-
E.
burnCapability
Indicates that an entity has the ability or potential to burn, ignite, or cause combustion under certain conditions.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df5b68481908a5d40516b09be52 |
completed | April 10, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:28 p.m.