Triple
T7930213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ODOT highways |
E184169
|
entity |
| Predicate | emergencyUse |
P79836
|
FINISHED |
| Object | evacuation routes in Oregon |
—
|
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: evacuation routes in Oregon | Statement: [ODOT highways, emergencyUse, evacuation routes in Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyUse Context triple: [ODOT highways, emergencyUse, evacuation routes in Oregon]
-
A.
emergencyRole
Indicates that an entity holds a specific function, responsibility, or authority in emergency or crisis situations.
-
B.
emergencyResponse
Indicates a relationship where an entity takes immediate action to address or manage an urgent or critical situation.
-
C.
emergencyPower
Indicates that an entity has backup or auxiliary power available or activated for use during emergencies or primary power failures.
-
D.
emergencyService
Indicates that one entity provides or is associated with urgent, time-critical assistance or response to another entity in emergency situations.
-
E.
emergencyEvent
Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3acb6cb88190b4f31b7091881241 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:07 p.m.