Triple

T8700868
Position Surface form Disambiguated ID Type / Status
Subject Cambourne E206526 entity
Predicate hasComponent P35 FINISHED
Object Great Cambourne E206526 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: Great Cambourne | Statement: [Cambourne, hasComponent, Great Cambourne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Great Cambourne
Context triple: [Cambourne, hasComponent, Great Cambourne]
  • A. Cambourne chosen
    Cambourne is a modern, rapidly growing new town in Cambridgeshire, England, developed in the late 20th century and known for its planned residential communities and local amenities.
  • B. Northbourne
    Northbourne is a small village and civil parish in Kent, England, known for its rural character and historic church.
  • C. Letcombe Regis
    Letcombe Regis is a small rural village in Oxfordshire, England, situated near the market town of Wantage on the edge of the Berkshire Downs.
  • D. Twyford
    Twyford is a village and civil parish in Berkshire, England, known as a commuter settlement between Reading and London.
  • E. Coxheath
    Coxheath is a large village in Kent, England, known historically for its role as a military camp and now as a residential community near Maidstone.
  • 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_69ca83555b6c8190abe930dd397e863b completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc58b27bd48190a5f76111ee657553 completed March 31, 2026, 11:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69cef41657588190ba6f79c27658dd1b completed April 2, 2026, 10:56 p.m.
Created at: March 30, 2026, 6:34 p.m.