Triple
T21236122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Delta (2005) |
E523347
|
entity |
| Predicate | isUnusuallyIntense |
P16069
|
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 Delta (2005), isUnusuallyIntense, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnusuallyIntense Context triple: [Hurricane Delta (2005), isUnusuallyIntense, true]
-
A.
isIntense
chosen
Indicates that something exhibits a high degree of strength, force, or concentration in its quality, effect, or activity.
-
B.
eraOfIncreasedIntensity
Indicates a period during which the level or strength of a particular activity, condition, or phenomenon becomes significantly higher than before.
-
C.
intensifiedOver
Indicates that one entity increases the degree, strength, or intensity of another entity or condition beyond its previous level.
-
D.
significantlyIntensifiedAfter
Indicates that one condition, effect, or quality became much stronger or more pronounced following another event or state.
-
E.
intensiveUse
Indicates a relationship where an entity is used in a concentrated, frequent, or high-intensity manner by another entity.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735202c7481909c642ddaafb40671 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:46 p.m.