Triple
T21105993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Epsilon |
E520044
|
entity |
| Predicate | dissipationDate |
P23027
|
FINISHED |
| Object | 2005-12-08 |
—
|
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-12-08 | Statement: [Hurricane Epsilon, dissipationDate, 2005-12-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissipationDate Context triple: [Hurricane Epsilon, dissipationDate, 2005-12-08]
-
A.
dissipatedOn
chosen
Indicates that something (such as energy, force, or a substance) is dispersed, lost, or converted into a less usable form on or within a particular medium, surface, or system.
-
B.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
-
C.
dissipatedIn
Indicates that something (such as energy, heat, or a substance) is lost, spread out, or converted within a particular medium, location, or system.
-
D.
dissipatedBy
Indicates that some quantity (such as energy, heat, or power) is lost, scattered, or converted into a less usable form by a particular agent or process.
-
E.
ruptureDate
Indicates the date on which a rupture event (such as a break, burst, or failure) occurs in the relationship between entities.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b62301c819082cfc6cb3cd11c8c |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.