Triple

T16900742
Position Surface form Disambiguated ID Type / Status
Subject Bewbush E424426 entity
Predicate hasNearbyNeighbourhood P4647 FINISHED
Object Broadfield E424658 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: Broadfield | Statement: [Bewbush, hasNearbyNeighbourhood, Broadfield]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Broadfield
Context triple: [Bewbush, hasNearbyNeighbourhood, Broadfield]
  • A. Broadfield chosen
    Broadfield is a residential neighbourhood and community area within the town of Crawley in West Sussex, England.
  • B. Blanefield
    Blanefield is a small village in central Scotland, situated near the Campsie Fells and known for its scenic rural setting within the Stirling area.
  • C. Willowbridge
    Willowbridge is a small rural settlement located within New Zealand’s Waimate District in the South Island.
  • D. Lanefield
    Lanefield is a rural locality within the Ipswich City Council area in Queensland, Australia, known for its agricultural land and small residential community.
  • E. Lakefield
    Lakefield is a small village in Ontario, Canada, known for its scenic setting along the Otonabee River and its historic, cottage-country character.
  • 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_69d889da3e8c8190a2b118f383f0beac completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3c8dbc6e48190be90066b82fc61db completed April 18, 2026, 6:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00cfcd0db8819080d415a18b3435e2 completed May 10, 2026, 6:34 p.m.
Created at: April 10, 2026, 5:29 a.m.