Triple

T5034112
Position Surface form Disambiguated ID Type / Status
Subject Pipp Brook E113378 entity
Predicate flowsThrough P225 FINISHED
Object Dorking E26185 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: Dorking | Statement: [Pipp Brook, flowsThrough, Dorking]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dorking
Context triple: [Pipp Brook, flowsThrough, Dorking]
  • A. Dorking chosen
    Dorking is a historic market town in southeast England, known for its scenic setting in the Surrey Hills and its traditional high street, vineyards, and surrounding countryside.
  • B. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • C. Purley
    Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
  • D. Chertsey
    Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
  • E. Burgess Hill
    Burgess Hill is a town in southeastern England known as a commuter hub with residential areas and light industry, situated within the county of West Sussex.
  • 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_69bd443775e48190a646ffbfc4334723 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73b8646c8190b3cc20193e4639ee completed March 20, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c5187dfe008190ac60e042527e55b3 completed March 26, 2026, 11:29 a.m.
Created at: March 20, 2026, 1:36 p.m.