Triple

T12405992
Position Surface form Disambiguated ID Type / Status
Subject Dedworth E296386 entity
Predicate hasNearbyArea P4647 FINISHED
Object Clewer E296387 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: Clewer | Statement: [Dedworth, hasNearbyArea, Clewer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clewer
Context triple: [Dedworth, hasNearbyArea, Clewer]
  • A. Clewer chosen
    Clewer is a suburban area and former village within the Royal Borough of Windsor and Maidenhead in Berkshire, England.
  • B. Tangmere
    Tangmere is a village in West Sussex, England, best known for its historic RAF airfield and aviation museum.
  • C. Dunsfold
    Dunsfold is a rural village in Surrey, England, known for its historic church and the nearby Dunsfold Aerodrome, a former WWII airfield now used for aviation and motoring events.
  • D. Cobham
    Cobham is a clan associated with the Efik people, an ethnic group primarily found in southeastern Nigeria.
  • E. 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.
  • 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_69d6ad9f464c81909db36d7e96e34b9e completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d48f1908190918551c794f98fe3 completed April 10, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f63486d1b881908d94218d2c391123 completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:55 p.m.