Triple

T13669450
Position Surface form Disambiguated ID Type / Status
Subject Chobham Common E327709 entity
Predicate locatedNear P294 FINISHED
Object Chobham E183742 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 | Statement: [Chobham Common, locatedNear, Chobham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chobham
Context triple: [Chobham Common, locatedNear, Chobham]
  • A. Chobham chosen
    Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
  • B. Cobham
    Cobham is a British aerospace and defense company known for supplying advanced air-to-air refueling systems and mission-critical communication technologies to military and civil aircraft programs worldwide.
  • C. Cobham
    Cobham is a historic village in north-west Kent, England, known for its traditional architecture, surrounding countryside, and notable landmarks such as Cobham Hall.
  • D. Cobham
    Cobham is a clan associated with the Efik people, an ethnic group primarily found in southeastern Nigeria.
  • E. Cobham
    Cobham is a village in Surrey, England, known for its affluent residential character, proximity to London, and scenic riverside setting.
  • 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_69d8076f1fa8819094664a59b55010df completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc65832688190aea688fee0a7cbdb completed April 12, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69fba1b4ae588190b293c71312ee4037 completed May 6, 2026, 8:16 p.m.
Created at: April 9, 2026, 9:53 p.m.