Triple

T6289360
Position Surface form Disambiguated ID Type / Status
Subject Painshill Park E140975 entity
Predicate locatedNear P294 FINISHED
Object Cobham E140975 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: Cobham | Statement: [Painshill Park, locatedNear, Cobham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cobham
Context triple: [Painshill Park, locatedNear, Cobham]
  • A. Cobham chosen
    Cobham is a village in Surrey, England, known for its affluent residential character, proximity to London, and scenic riverside setting.
  • B. Cobham
    Cobham is a clan associated with the Efik people, an ethnic group primarily found in southeastern Nigeria.
  • C. Chobham
    Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
  • D. Camberley
    Camberley is a suburban town in southeast England known for its shopping centre, commuter links to London, and proximity to the Royal Military Academy Sandhurst.
  • E. Beckenham
    Beckenham is a suburban town in southeast London known for its residential character, green spaces, and commuter links into central London.
  • 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_69c008cd17c8819082b82d3fbeb68047 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0641a6ecc8190a63be0e3f0344a3f completed March 22, 2026, 9:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c640a7ef8881909b00ce1f479f0fb4 completed March 27, 2026, 8:32 a.m.
Created at: March 22, 2026, 4:26 p.m.