Triple

T16903890
Position Surface form Disambiguated ID Type / Status
Subject Stoke D'Abernon E424506 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: [Stoke D'Abernon, locatedNear, Cobham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cobham
Context triple: [Stoke D'Abernon, 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. 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.
  • D. 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.
  • E. Chobham
    Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
  • 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_69d889da3e8c8190a2b118f383f0beac completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e3c8de3070819085bfe9696bc887ea completed April 18, 2026, 6:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00cfcedb58819087c31200c01f40b7 completed May 10, 2026, 6:34 p.m.
Created at: April 10, 2026, 5:30 a.m.