Triple
T37308604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Atlantic wave climate |
E926143
|
entity |
| Predicate | includesExtreme |
P205832
|
FINISHED |
| Object | storm waves |
—
|
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: storm waves | Statement: [North Atlantic wave climate, includesExtreme, storm waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesExtreme Context triple: [North Atlantic wave climate, includesExtreme, storm waves]
-
A.
isExtensiveIn
Indicates that one entity is widespread, far-reaching, or broadly distributed within, across, or throughout another entity or domain.
-
B.
hasExtensive
Indicates that one entity possesses a large, wide-ranging, or comprehensive amount or degree of another entity or attribute.
-
C.
isExtremal
Indicates that an entity represents an extreme (such as a maximum, minimum, or boundary) within a given set, structure, or ordering.
-
D.
extremalCase
Indicates a relationship where a situation, value, or configuration represents the most extreme or boundary case within a given set, range, or conditions.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:16 p.m.