Triple

T13549044
Position Surface form Disambiguated ID Type / Status
Subject Hurst Castle E323592 entity
Predicate locatedNear P294 FINISHED
Object Milford on Sea E926226 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: Milford on Sea | Statement: [Hurst Castle, locatedNear, Milford on Sea]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Milford on Sea
Context triple: [Hurst Castle, locatedNear, Milford on Sea]
  • A. Milford on Sea chosen
    Milford on Sea is a coastal village in Hampshire, England, known for its beaches, views across the Solent to the Isle of Wight, and proximity to the New Forest National Park.
  • B. Stourmouth
    Stourmouth is a small rural village in Kent, England, situated near the River Stour and known for its historic church and countryside setting.
  • C. Havenpool
    Havenpool is a fictional town in Thomas Hardy’s Wessex, based on the real port of Poole on England’s south coast.
  • D. Westgate-on-Sea
    Westgate-on-Sea is a small seaside town on the north coast of Kent, England, known for its sandy beaches and Victorian architecture.
  • E. Burnham-on-Sea
    Burnham-on-Sea is a small seaside resort town on the Bristol Channel coast of Somerset in southwest England, known for its sandy beaches and historic low lighthouse.
  • 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_69d8076776248190bdf0d4fa1f85a5fc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafdcecf481909999a173b32a58cd completed April 12, 2026, 2:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75da4e19c819090d649b60a2dd410 completed May 3, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:45 p.m.