Triple

T7912906
Position Surface form Disambiguated ID Type / Status
Subject Chobham E183742 entity
Predicate contains P35 FINISHED
Object Chobham Common E327709 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: Chobham Common | Statement: [Chobham, contains, Chobham Common]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chobham Common
Context triple: [Chobham, contains, Chobham Common]
  • A. Chobham Common chosen
    Chobham Common is a large lowland heathland nature reserve in Surrey, England, known for its rare wildlife and protected habitats.
  • B. Sutton Common
    Sutton Common is a local open green space in the London Borough of Sutton, providing recreational and leisure areas for the surrounding community.
  • C. Hindhead Common
    Hindhead Common is a large heathland and woodland area in Surrey, England, known for its scenic views, walking trails, and conservation of rare wildlife habitats.
  • D. Oldland Common
    Oldland Common is a village and residential area in South Gloucestershire, England, known for its suburban character and proximity to Bristol.
  • E. Letchmore Heath
    Letchmore Heath is a small, picturesque village in Hertfordshire, England, known for its traditional village green and historic rural character.
  • 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_69ca828dec0c81908b8f55a4dbbb53ff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a7383cc819084eab19799209d2e completed March 31, 2026, 3:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5bdfb8d0819089cf1268df61bcdc completed March 31, 2026, 5:30 a.m.
Created at: March 30, 2026, 5:04 p.m.