Triple

T6050629
Position Surface form Disambiguated ID Type / Status
Subject C Branch E134782 entity
Predicate servesNeighborhood P82 FINISHED
Object Brighton E177150 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 | Statement: [C Branch, servesNeighborhood, Brighton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brighton
Context triple: [C Branch, servesNeighborhood, Brighton]
  • A. Brighton
    Brighton is a major seaside city on England’s south coast, renowned for its beach, pier, and vibrant cultural and nightlife scenes.
  • B. Brighton
    Brighton is a small city in Colorado that forms part of the Denver metropolitan area along the Front Range of the Rocky Mountains.
  • C. Brighton chosen
    Brighton is a residential neighborhood in the western part of Boston, Massachusetts, known for its mix of students, young professionals, and long-time residents.
  • D. Brighton
    Brighton is a small mountain resort town in Utah known for its ski area, alpine scenery, and outdoor recreation.
  • 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_69c00877b6d4819096b0e163728b73a3 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c056f66cb08190a782cdd038f26b93 completed March 22, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1133e346881909a3c07c692f8ef54 completed March 23, 2026, 10:17 a.m.
Created at: March 22, 2026, 4:09 p.m.