Triple

T2952631
Position Surface form Disambiguated ID Type / Status
Subject Brixham shipyard E79855 entity
Predicate locatedIn P40 FINISHED
Object Brixham E81723 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: Brixham | Statement: [Brixham shipyard, locatedIn, Brixham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brixham
Context triple: [Brixham shipyard, locatedIn, Brixham]
  • A. Brixham chosen
    Brixham is a historic fishing town and port in Devon, England, known for its maritime heritage and role in traditional shipbuilding.
  • B. Torquay
    Torquay is a seaside resort town on the English Riviera in Devon, England, known for its mild climate, beaches, and Victorian-era tourism.
  • C. Exmouth
    Exmouth is a coastal town in Devon, England, known as a popular seaside resort at the mouth of the River Exe.
  • D. Torbay
    Torbay is a coastal unitary authority and popular seaside resort area in Devon, England, encompassing the towns of Torquay, Paignton, and Brixham.
  • E. Nailsea
    Nailsea is a small town in North Somerset, England, historically known for its glassmaking and coal mining industries.
  • 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_69ad8b1276588190a374a0b12e0f7bdf completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad98fe4b688190a0f68c4f80cd6f8f completed March 8, 2026, 3:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69b1de92f04c8190967ec290cba891a6 completed March 11, 2026, 9:28 p.m.
Created at: March 8, 2026, 2:57 p.m.