Triple

T17727767
Position Surface form Disambiguated ID Type / Status
Subject Hullbridge E442507 entity
Predicate locatedNear P294 FINISHED
Object Rayleigh 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: Rayleigh | Statement: [Hullbridge, locatedNear, Rayleigh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rayleigh
Context triple: [Hullbridge, locatedNear, Rayleigh]
  • A. Rayleigh chosen
    Rayleigh is a historic market town in the county of Essex, England, known for its medieval roots and prominent hilltop location.
  • B. Sandys
    Sandys is the surname of Frederic Sandys, a 19th-century British painter and illustrator associated with the Pre-Raphaelite movement.
  • C. Bayliss
    Bayliss is a small unincorporated rural community located in Glenn County, California.
  • D. Leamouth
    Leamouth is a riverside district in East London where the River Lea meets the River Thames, known for its former industrial docks and recent waterside redevelopment.
  • E. Hartley
    Hartley is a village in north-west Kent, England, known for its rural character and residential communities within commuting distance of London.
  • 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_69d8b9ec79688190b86bdcef85a7b3aa completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e478e3cb708190b47456ad2008a65e completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 10:07 a.m.