Triple

T18283353
Position Surface form Disambiguated ID Type / Status
Subject RAF Binbrook E437917 entity
Predicate locatedIn P40 FINISHED
Object Binbrook 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: Binbrook | Statement: [RAF Binbrook, locatedIn, Binbrook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Binbrook
Context triple: [RAF Binbrook, locatedIn, Binbrook]
  • A. Binbrook chosen
    Binbrook is a small rural village in Lincolnshire, England, known historically for its agricultural setting and former RAF airfield.
  • B. Southbroom
    Southbroom is a coastal holiday village in KwaZulu-Natal, South Africa, known for its beaches, golf course, and relaxed resort atmosphere.
  • C. Bilbrook
    Bilbrook is a village in Staffordshire, England, known as the place where geneticist Reginald Punnett died.
  • D. Huonbrook
    Huonbrook is a rural locality in the hinterland of New South Wales, Australia, known for its forested valleys, creeks, and alternative lifestyle communities.
  • E. Brookton
    Brookton is a small rural town in Western Australia's Wheatbelt region, known for its grain farming and agricultural services.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e500f7ff088190933bb8f403ce7f9c completed April 19, 2026, 4:21 p.m.
Created at: April 10, 2026, 10:35 a.m.