Triple

T28865237
Position Surface form Disambiguated ID Type / Status
Subject Filey Coble Landing E728978 entity
Predicate coastManagement P103616 FINISHED
Object local authority managed area 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: local authority managed area | Statement: [Filey Coble Landing, coastManagement, local authority managed area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coastManagement
Context triple: [Filey Coble Landing, coastManagement, local authority managed area]
  • A. hasCoastManagement chosen
    Indicates that an entity is responsible for or involved in the management, regulation, or oversight of coastal areas or coastal resources in relation to another entity or region.
  • B. coastalHub
    Indicates a location functions as a primary center of activity, transport, or services situated on or very near a coastline.
  • C. coastalProtection
    Indicates measures or actions taken to preserve, defend, or stabilize coastal areas against erosion, flooding, or other marine-related impacts.
  • D. coastalInteraction
    Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
  • E. shorelineDevelopment
    Indicates the extent to which human-made structures or modifications have been built along a shoreline.
  • 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_69f031a01cbc8190ba87270bb6fe4639 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f65b14512c8190a40e70319dcc54cd completed May 2, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69f659d02f1c8190831758ac52bb54e4 completed May 2, 2026, 8:08 p.m.
Created at: April 28, 2026, 6:48 a.m.