Triple

T871025
Position Surface form Disambiguated ID Type / Status
Subject Horley E18812 entity
Predicate isCommuterTownFor P5065 FINISHED
Object Brighton 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 | Statement: [Horley, isCommuterTownFor, Brighton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brighton
Context triple: [Horley, isCommuterTownFor, Brighton]
  • A. Brighton chosen
    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. Bristol
    Bristol is a historic port city in southwest England known for its maritime heritage, vibrant cultural scene, and distinctive Georgian and Victorian architecture.
  • D. Southampton
    Southampton is a major port city on England’s south coast, historically significant for its maritime trade, shipbuilding, and role as a departure point for transatlantic voyages.
  • E. Southampton
    Southampton is a wealthy town and popular seaside resort community on the South Fork of Long Island, New York, known for its beaches, historic villages, and part of the Hamptons.
  • 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_69a4938db1f081909bcd1ad2713b6096 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac94d5ac81909feee876696da589 completed March 1, 2026, 9:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac7f23e10081909ebf4e87dc081254 completed March 7, 2026, 7:40 p.m.
Created at: March 1, 2026, 7:39 p.m.