Triple

T7142338
Position Surface form Disambiguated ID Type / Status
Subject Wadhurst E166475 entity
Predicate near P350 FINISHED
Object Ticehurst E556312 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: Ticehurst | Statement: [Wadhurst, near, Ticehurst]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ticehurst
Context triple: [Wadhurst, near, Ticehurst]
  • A. Ticehurst chosen
    Ticehurst is a rural village and civil parish in East Sussex, England, known for its historic architecture and surrounding countryside.
  • B. Wadhurst
    Wadhurst is a rural village in East Sussex, England, known for its historic High Street, surrounding Wealden countryside, and role as a commuter community for nearby towns and London.
  • C. Uckfield
    Uckfield is a small market town in East Sussex, England, known for its historic high street and role as a local commercial and commuter hub.
  • D. Rustington
    Rustington is a large coastal village and civil parish on the English Channel in the Arun District of West Sussex, England.
  • E. Billingshurst
    Billingshurst is a large village and civil parish in the Horsham District of West Sussex, England, known for its historic High Street and role as a local residential and commercial centre.
  • 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_69c6888579d481909e05a8d6b81bf733 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e779ace48190be9c33750e60a79e completed March 27, 2026, 8:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ad98576481908b8b82f675079fca completed March 28, 2026, 10:29 a.m.
Created at: March 27, 2026, 2:45 p.m.