Triple
T24428558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picher, Oklahoma |
E615928
|
entity |
| Predicate | evacuationRecommendedBy |
P86150
|
FINISHED |
| Object | U.S. Army Corps of Engineers |
—
|
NE NERFINISHED |
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: U.S. Army Corps of Engineers | Statement: [Picher, Oklahoma, evacuationRecommendedBy, U.S. Army Corps of Engineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuationRecommendedBy Context triple: [Picher, Oklahoma, evacuationRecommendedBy, U.S. Army Corps of Engineers]
-
A.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
B.
evacuationOrderIssuedBy
chosen
Indicates that a specific authority or organization has formally issued an evacuation order for people to leave a particular area.
-
C.
evacuationOrderedIn
Indicates that an official evacuation has been ordered to occur within a specified location or area.
-
D.
evacuationReason
Indicates the cause or justification for why an evacuation took place or was required.
-
E.
evacuationPoint
Indicates a location designated as the place where people should gather or be moved to during an evacuation.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a983d88190904b559694363a19 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.