Triple

T8584387
Position Surface form Disambiguated ID Type / Status
Subject Comberton E203265 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Hardwick E203267 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: Hardwick | Statement: [Comberton, hasNearbySettlement, Hardwick]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hardwick
Context triple: [Comberton, hasNearbySettlement, Hardwick]
  • A. Hardwick chosen
    Hardwick is a village and civil parish in the South Cambridgeshire district of Cambridgeshire, England.
  • B. Hardwick
    Hardwick is an English country estate in Derbyshire best known for its grand Elizabethan mansion, Hardwick Hall, historically associated with the Cavendish family.
  • C. Hardwick
    Hardwick is an English-origin surname borne by various notable individuals across fields such as sports, politics, and the arts.
  • D. Hardwick
    Hardwick is a small settlement in Oxfordshire, England, forming part of the civil parish of Ducklington.
  • E. Willowbridge
    Willowbridge is a small rural settlement located within New Zealand’s Waimate District in the South Island.
  • 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_69ca8329bb7c8190a63c643730839103 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbeb1ecc188190bbe2ab8d2423505b completed March 31, 2026, 3:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce89bfb95c81909660460d5813fdaf completed April 2, 2026, 3:22 p.m.
Created at: March 30, 2026, 6:22 p.m.