Triple

T8706209
Position Surface form Disambiguated ID Type / Status
Subject Regatta at Molesey E206656 entity
Predicate location depicted P8908 FINISHED
Object Molesey E25826 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: Molesey | Statement: [Regatta at Molesey, location depicted, Molesey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Molesey
Context triple: [Regatta at Molesey, location depicted, Molesey]
  • A. Molesey chosen
    Molesey is a suburban town in south-east England situated on the River Thames, known for its proximity to Hampton Court Palace and its residential character within the London commuter belt.
  • B. Moorfield
    Moorfield is a given name most notably borne by Moorfield Storey, an American lawyer and civil rights leader who served as the first president of the NAACP.
  • C. Biddenden
    Biddenden is a historic village in Kent, England, known for its traditional Wealden architecture, vineyards, and the local legend of the Biddenden Maids.
  • D. Hellingly
    Hellingly is a village and civil parish in East Sussex, England, known for its rural character and historic parish church.
  • E. Willingdon
    Willingdon is a village in East Sussex, England, situated near the town of Hailsham.
  • 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_69ca835645e881908f00e3c8b51da81d completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc58fcac748190a82b57aeb7c43df9 completed March 31, 2026, 11:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69cef423b1c4819081ea887af8f8e576 completed April 2, 2026, 10:56 p.m.
Created at: March 30, 2026, 6:35 p.m.