Triple

T871042
Position Surface form Disambiguated ID Type / Status
Subject Horley E18812 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object Redhill E23394 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: Redhill | Statement: [Horley, hasNeighbouringSettlement, Redhill]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Redhill
Context triple: [Horley, hasNeighbouringSettlement, Redhill]
  • A. Redhill chosen
    Redhill is a commuter town in southeast England known for its transport links and proximity to London within the county of Surrey.
  • B. Petworth
    Petworth is a historic market town in South East England, noted for its stately home Petworth House and surrounding deer park.
  • C. Petworth
    Petworth is a primarily residential neighborhood in the northwestern part of Washington, D.C., known for its row houses, community-oriented atmosphere, and growing mix of local businesses.
  • D. Banstead
    Banstead is a suburban town in southeast England known for its village-like high street and green spaces within the county of Surrey.
  • E. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • 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_69a4938db1f081909bcd1ad2713b6096 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac94d5ac81909feee876696da589 completed March 1, 2026, 9:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69acbad10ae48190af7dcaa8dfff30ec completed March 7, 2026, 11:54 p.m.
Created at: March 1, 2026, 7:39 p.m.