Triple

T3655688
Position Surface form Disambiguated ID Type / Status
Subject Keppel E77523 entity
Predicate contains P35 FINISHED
Object Farnborough E98735 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: Farnborough | Statement: [Keppel, contains, Farnborough]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Farnborough
Context triple: [Keppel, contains, Farnborough]
  • A. Farnborough, London
    Farnborough, London is a suburban area in the London Borough of Bromley known for its village-like character on the southeastern edge of Greater London.
  • B. Farnborough Airfield chosen
    Farnborough Airfield is a historic British airfield in Hampshire renowned as a major center for aviation research, development, and the famous Farnborough International Airshow.
  • C. Maidenhead
    Maidenhead is a large riverside town on the River Thames in Berkshire, England, known as a commuter hub for London with a mix of historic and modern development.
  • 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_69ad85def5cc8190863dccf55a18bebb completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc3baf57c8190b72b5d1b910d9db6 completed March 8, 2026, 6:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4883dc5408190a6e7e110acf03a15 completed March 13, 2026, 9:57 p.m.
Created at: March 8, 2026, 3:24 p.m.