Triple

T16711119
Position Surface form Disambiguated ID Type / Status
Subject Hornsea E406107 entity
Predicate isPartOf P10 FINISHED
Object Holderness E406108 NE 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: Holderness | Statement: [Hornsea, isPartOf, Holderness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holderness
Context triple: [Hornsea, isPartOf, Holderness]
  • A. Holderness chosen
    Holderness is a low-lying coastal region in the East Riding of Yorkshire, England, known for its rapidly eroding North Sea coastline and agricultural landscape.
  • B. Farlington
    Farlington is a small rural village in North Yorkshire, England, situated near the River Foss and known for its historic parish church and agricultural surroundings.
  • C. Farlington
    Farlington is a residential suburb in the northern part of Portsmouth, England, known for its coastal location and access to major transport routes.
  • D. Forsbrook
    Forsbrook is a village and civil parish in Staffordshire, England, situated near the edge of the Staffordshire Moorlands.
  • E. Parkeston
    Parkeston is a village and port area in Essex, England, situated near Harwich and known historically for its railway and maritime connections.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e386523fc08190a13a4232af191992 completed April 18, 2026, 1:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0091a95180819099abd50dd153e229 completed May 10, 2026, 2:09 p.m.
Created at: April 10, 2026, 5:20 a.m.