Triple
T1065072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Katrina |
E22990
|
entity |
| Predicate | reachedCategory5On |
P23033
|
FINISHED |
| Object | 2005-08-28 |
—
|
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: 2005-08-28 | Statement: [Hurricane Katrina, reachedCategory5On, 2005-08-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedCategory5On Context triple: [Hurricane Katrina, reachedCategory5On, 2005-08-28]
-
A.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
C.
successorCategory
Indicates that one category directly follows or replaces another in an ordered sequence or hierarchy.
-
D.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
E.
reachedPeakUnder
Indicates that an entity achieved its highest level of success, performance, or influence during the tenure or leadership period of another entity.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b90f91248190ace1534a51b82bdd |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.