Triple
T16711158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holderness |
E406108
|
entity |
| Predicate | coastalErosionRate |
P113629
|
FINISHED |
| Object | among highest in Europe |
—
|
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: among highest in Europe | Statement: [Holderness, coastalErosionRate, among highest in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalErosionRate Context triple: [Holderness, coastalErosionRate, among highest in Europe]
-
A.
erosionRate
chosen
Indicates the rate at which material is worn away or removed from a surface over time due to erosive processes.
-
B.
coastalProtection
Indicates measures or actions taken to preserve, defend, or stabilize coastal areas against erosion, flooding, or other marine-related impacts.
-
C.
coastalInteraction
Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
-
D.
cliffStability
Indicates the degree to which a cliff is structurally secure and resistant to collapse or erosion under current conditions.
-
E.
erosionAgent
Indicates the natural force or process responsible for wearing away, transporting, or reshaping material from a surface.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e386523fc08190a13a4232af191992 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.