Triple
T12708661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covehithe |
E303654
|
entity |
| Predicate | shorelineProcess |
P71569
|
FINISHED |
| Object | coastal erosion |
—
|
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: coastal erosion | Statement: [Covehithe, shorelineProcess, coastal erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineProcess Context triple: [Covehithe, shorelineProcess, coastal erosion]
-
A.
shorelineDevelopment
Indicates the extent to which human-made structures or modifications have been built along a shoreline.
-
B.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
C.
shorelineCharacteristic
chosen
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
D.
formsShorelineOf
Indicates that one geographic feature constitutes or defines the boundary or edge (shoreline) of a body of water.
-
E.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96207b2d881908314efc3e350aa78 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.