Triple
T1065117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Katrina |
E22990
|
entity |
| Predicate | notableAnniversary |
P8485
|
FINISHED |
| Object | 10th anniversary commemorations in 2015 |
—
|
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: 10th anniversary commemorations in 2015 | Statement: [Hurricane Katrina, notableAnniversary, 10th anniversary commemorations in 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAnniversary Context triple: [Hurricane Katrina, notableAnniversary, 10th anniversary commemorations in 2015]
-
A.
completionAnniversary
Indicates the date or event marking the anniversary of when something was originally completed.
-
B.
typeOfAnniversary
Indicates the specific category or kind of anniversary that an event or date represents (e.g., wedding, work, founding).
-
C.
anniversaryNumber
chosen
Indicates the specific ordinal count of an anniversary occurrence in a recurring commemorative event or relationship.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
- 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_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. |
Created at: March 1, 2026, 7:42 p.m.