Triple
T19246771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dungeness |
E481278
|
entity |
| Predicate | hasClimateNote |
P32804
|
FINISHED |
| Object | exposed coastal climate |
—
|
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: exposed coastal climate | Statement: [Dungeness, hasClimateNote, exposed coastal climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimateNote Context triple: [Dungeness, hasClimateNote, exposed coastal climate]
-
A.
hasClimate
Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
-
B.
hasClimateContext
chosen
Indicates that something is associated with, influenced by, or relevant to climate-related conditions, factors, or considerations.
-
C.
hasClimateInfluence
Indicates that one entity affects or contributes to the climate characteristics or climate-related conditions of another entity.
-
D.
hasExtremeWeatherCharacteristic
Indicates that something possesses a notable or defining feature related to extreme weather conditions.
-
E.
climateBetween
Indicates that something (such as a location, period, or condition) has a climate that lies within a specified range or intermediate state between two other climatic conditions.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2daacc8190b8af99dee51f238d |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.