Triple

T13879787
Position Surface form Disambiguated ID Type / Status
Subject Fylde district E333682 entity
Predicate contains P35 FINISHED
Object Wesham E964642 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: Wesham | Statement: [Fylde district, contains, Wesham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wesham
Context triple: [Fylde district, contains, Wesham]
  • A. Wesham chosen
    Wesham is a small town in Lancashire, England, situated near major transport links and forming part of the wider Fylde borough.
  • B. Barsham
    Barsham is a small rural village and civil parish located in the English county of Suffolk.
  • C. Sallum
    Sallum is a small Egyptian border town on the Mediterranean coast near Libya, known as a key crossing point and coastal settlement in Egypt’s western desert region.
  • D. Waghala
    Waghala is a town in Maharashtra, India, that forms part of the urban area administered by the Nanded-Waghala City Municipal Corporation.
  • E. Shendam
    Shendam is a historic town and local government area in central Nigeria known as one of the oldest settlements in Plateau State and a regional administrative and commercial center.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0be71d388190909290cad2c6daf5 completed April 14, 2026, 9:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c7100b308190bdd5feaa116ee5fe completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:15 p.m.