Triple
T21106001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Epsilon |
E520044
|
entity |
| Predicate | unusuallyLongLived |
P119937
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hurricane Epsilon, unusuallyLongLived, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unusuallyLongLived Context triple: [Hurricane Epsilon, unusuallyLongLived, true]
-
A.
longLived
chosen
Indicates that an entity has a lifespan or duration of existence significantly longer than what is typical or expected in its context.
-
B.
heldForLife
Indicates that something is possessed, controlled, or held by an entity for the entire duration of that entity’s life, without transfer or expiration before death.
-
C.
enduringLegacy
Indicates that something continues to have a lasting influence, impact, or significance well beyond its original time or context.
-
D.
isLongStanding
Indicates that a relationship, condition, or state has existed for a considerable or extended period of time.
-
E.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
- 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.