Triple

T14021718
Position Surface form Disambiguated ID Type / Status
Subject Burstow E337347 entity
Predicate near P350 FINISHED
Object Horley E18812 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: Horley | Statement: [Burstow, near, Horley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horley
Context triple: [Burstow, near, Horley]
  • A. Horley chosen
    Horley is a town in southeast England situated near Gatwick Airport, known as a commuter hub between London and the Sussex coast.
  • B. Ferryhill
    Ferryhill is a small town in County Durham, England, known historically for its coal mining heritage and location between Durham and Darlington.
  • C. Wakefield
    Wakefield is a historic cathedral city in West Yorkshire, Northern England, known for its medieval heritage and role as an administrative and commercial center in the region.
  • D. Wakefield
    Wakefield is a picturesque village in western Quebec, Canada, known for its historic covered bridge, arts community, and scenic setting along the Gatineau River.
  • E. Wakefield
    Wakefield is a small rural township in New Zealand’s Tasman District, located southwest of Nelson and serving as a local service and farming community.
  • 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2f3c7cd88190b236382058581740 completed April 14, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc32f78dc8190bd357d179cbaa5bc completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:19 p.m.