Triple
T19175574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Fire |
E469427
|
entity |
| Predicate | promptedAction |
P134741
|
FINISHED |
| Object | mass evacuations in Butte County |
—
|
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: mass evacuations in Butte County | Statement: [Camp Fire, promptedAction, mass evacuations in Butte County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promptedAction Context triple: [Camp Fire, promptedAction, mass evacuations in Butte County]
-
A.
promptedDemandFor
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
-
B.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
C.
attemptedAction
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
D.
plannedAction
Indicates that an action is intended or scheduled to occur in the future, but has not yet been executed.
-
E.
promptType
Indicates the specific category or style of a prompt that characterizes how an instruction or request is framed or intended to be interpreted.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f166d3888190adaf6dc8531a8ed1 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.