Triple

T36259007
Position Surface form Disambiguated ID Type / Status
Subject Gunby, Lincolnshire E892028 entity
Predicate hasNearestSeasideResort P95431 FINISHED
Object Skegness NE NERFINISHED

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: Skegness | Statement: [Gunby, Lincolnshire, hasNearestSeasideResort, Skegness]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearestSeasideResort
Context triple: [Gunby, Lincolnshire, hasNearestSeasideResort, Skegness]
  • A. hasBeachNearby chosen
    Indicates that one location is situated close enough to another location to have convenient access to a beach.
  • B. isSeasideResort
    Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
  • C. hasBeachResorts
    Indicates that a place possesses or is home to one or more beach resorts.
  • D. hasShoreNear
    Indicates that one entity is located close enough to another entity’s shore or coastline to be considered nearby.
  • E. hasCoastlineResort
    Indicates that a geographic area or location contains a resort situated along its coastline.
  • 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_69f76e4699188190af045b11a840ce31 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a00512437d48190ad20324968ead5f4 completed May 10, 2026, 9:34 a.m.
PD Predicate disambiguation batch_6a0050227350819099f41369c3d168be completed May 10, 2026, 9:30 a.m.
Created at: May 3, 2026, 4:09 p.m.