Triple

T6603477
Position Surface form Disambiguated ID Type / Status
Subject Southwick E149058 entity
Predicate adjacentTo P224 FINISHED
Object Brighton and Hove E45112 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: Brighton and Hove | Statement: [Southwick, adjacentTo, Brighton and Hove]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brighton and Hove
Context triple: [Southwick, adjacentTo, Brighton and Hove]
  • A. Brighton
    Brighton is a residential neighborhood in the western part of Boston, Massachusetts, known for its mix of students, young professionals, and long-time residents.
  • B. Brighton
    Brighton is a small mountain resort town in Utah known for its ski area, alpine scenery, and outdoor recreation.
  • C. Brighton chosen
    Brighton is a major seaside city on England’s south coast, renowned for its beach, pier, and vibrant cultural and nightlife scenes.
  • D. Brighton
    Brighton is a small city in Colorado that forms part of the Denver metropolitan area along the Front Range of the Rocky Mountains.
  • E. Brighton
    Brighton is a residential neighborhood in Seattle’s Rainier Valley known for its diversity and proximity to parks and schools.
  • 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_69c687eaa7508190bb58ce2aa02039b3 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6af11f0788190be010c6ee60e150c completed March 27, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c712841eb4819098057a290520254e completed March 27, 2026, 11:28 p.m.
Created at: March 27, 2026, 1:56 p.m.