Triple

T18562264
Position Surface form Disambiguated ID Type / Status
Subject Foxton Beach E453674 entity
Predicate near P350 FINISHED
Object Foxton 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: Foxton | Statement: [Foxton Beach, near, Foxton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Foxton
Context triple: [Foxton Beach, near, Foxton]
  • A. Foxton
    Foxton is a small village and civil parish in South Cambridgeshire, England, known for its rural character and proximity to Cambridge.
  • B. Foxton chosen
    Foxton is a small coastal town in New Zealand known for its historic flax industry and proximity to the Manawatū River.
  • C. 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.
  • D. Farlington
    Farlington is a residential suburb in the northern part of Portsmouth, England, known for its coastal location and access to major transport routes.
  • E. Fordsburg
    Fordsburg is a historic, culturally diverse suburb of Johannesburg known for its strong Indian and Muslim community, bustling markets, and vibrant street life.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38974308190a9174430ef256b73 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53afb4f088190adf0b2b64057a210 completed April 19, 2026, 8:28 p.m.
Created at: April 10, 2026, 11:42 a.m.