Triple
T38487064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Gilbert |
E917945
|
entity |
| Predicate | remnantsAffected |
P190953
|
FINISHED |
| Object | Midwestern United States |
—
|
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: Midwestern United States | Statement: [Hurricane Gilbert, remnantsAffected, Midwestern United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remnantsAffected Context triple: [Hurricane Gilbert, remnantsAffected, Midwestern United States]
-
A.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
B.
remnantUsedBy
Indicates that a remaining part or leftover of something is utilized or employed by another entity.
-
C.
remnantsInclude
Indicates that the remaining parts or leftovers of one entity contain or consist of another entity.
-
D.
remnantType
Indicates the specific kind or category of remnant that results from or is associated with an entity or process.
-
E.
remnantInteraction
Indicates an interaction where one entity engages with or is affected by the leftover, residual, or remaining part of another entity or process.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd31227708190a7df213597e66ca8 |
completed | May 7, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.