Triple

T12988166
Position Surface form Disambiguated ID Type / Status
Subject Kessingland Beach E321822 entity
Predicate partOf P40 FINISHED
Object Kessingland E299696 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: Kessingland | Statement: [Kessingland Beach, partOf, Kessingland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kessingland
Context triple: [Kessingland Beach, partOf, Kessingland]
  • A. Kessingland chosen
    Kessingland is a coastal village and civil parish in Suffolk, England, known for its long shingle beach and seaside tourism.
  • B. Tesseney
    Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
  • C. Birkholm
    Birkholm is a small, sparsely populated Danish island known for its tranquil natural environment and traditional village atmosphere in the South Funen Archipelago.
  • D. Hellingly
    Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
  • E. Kildonan
    Kildonan is a small settlement on the island of South Uist in Scotland’s Outer Hebrides.
  • 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_69d8076479b8819090afce3591939cdf completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e5f47ec8190b39107bc016f9824 completed April 10, 2026, 10:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6b8f942588190b69a3067d5145182 completed May 3, 2026, 2:54 a.m.
Created at: April 9, 2026, 8:42 p.m.