Triple
T3261474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oroville Dam |
E68419
|
entity |
| Predicate | evacuationOrderDate |
P41990
|
FINISHED |
| Object | February 2017 |
—
|
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: February 2017 | Statement: [Oroville Dam, evacuationOrderDate, February 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationOrderDate Context triple: [Oroville Dam, evacuationOrderDate, February 2017]
-
A.
evacuationDate
chosen
Indicates the date on which an evacuation occurs or is scheduled to occur.
-
B.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
C.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
D.
evacuationMethod
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
-
E.
notableEvacuation
Indicates a significant, widely recognized instance of people being moved or fleeing from a place for safety, typically due to danger or emergency conditions.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafa7fea08190b089b6174fd7cd32 |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.