Triple
T34603166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newbiggin breakwater |
E888520
|
entity |
| Predicate | coastTypeProtected |
P179685
|
FINISHED |
| Object | sandy bay |
—
|
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: sandy bay | Statement: [Newbiggin breakwater, coastTypeProtected, sandy bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastTypeProtected Context triple: [Newbiggin breakwater, coastTypeProtected, sandy bay]
-
A.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
B.
hasCoastlineDesignation
Indicates that a geographic area’s coastline has been assigned a specific official classification or status.
-
C.
marineProtectedAreaOf
Indicates that one entity is designated as a marine protected area that encompasses, is associated with, or provides protection for the other entity.
-
D.
protectedAreaOnShore
Indicates that a protected area is located on or along a shoreline.
-
E.
marineProtectedArea
Indicates that an area of marine or coastal waters is designated and managed to conserve natural resources and biodiversity, often restricting certain human activities.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2:03 a.m.