Triple
T24919024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrane |
E624067
|
entity |
| Predicate | coastProtection |
P41538
|
FINISHED |
| Object | sea defences |
—
|
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: sea defences | Statement: [Portrane, coastProtection, sea defences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastProtection Context triple: [Portrane, coastProtection, sea defences]
-
A.
coastalProtection
chosen
Indicates measures or actions taken to preserve, defend, or stabilize coastal areas against erosion, flooding, or other marine-related impacts.
-
B.
coastalDefense
Indicates a defensive relationship in which structures, systems, or actions are used to protect a coastline or shore area from threats such as erosion, flooding, or attack.
-
C.
hasCoastalProtectionConcern
Indicates that an entity has an issue, risk, or consideration related to protecting coastal areas from environmental or human impacts.
-
D.
shorelineDevelopment
Indicates the extent to which human-made structures or modifications have been built along a shoreline.
-
E.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4238e43c08190be03e813b8cdfe28 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:28 a.m.