Triple

T12864082
Position Surface form Disambiguated ID Type / Status
Subject Turville Hill E307670 entity
Predicate near P350 FINISHED
Object Ibstone E997336 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: Ibstone | Statement: [Turville Hill, near, Ibstone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ibstone
Context triple: [Turville Hill, near, Ibstone]
  • A. Ibstone chosen
    Ibstone is a small rural village in Buckinghamshire, England, situated in the Chiltern Hills and known for its scenic countryside and traditional English character.
  • B. Pitstone
    Pitstone is a village and civil parish in Buckinghamshire, England, known for its rural setting near the Chiltern Hills and proximity to the Grand Union Canal.
  • C. Isbister
    Isbister is a small coastal settlement on the island of Whalsay in the Shetland Islands of Scotland.
  • D. Sherkston
    Sherkston is a lakeside community in Ontario, Canada, known for its beaches, campgrounds, and recreational resort atmosphere along Lake Erie.
  • E. Orlestone
    Orlestone is a civil parish and rural community in the Ashford district of Kent, England, known for its woodland and countryside character.
  • 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_69d7bdf69bc48190af6c2621f28ca351 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9708cf6b48190886a99e04d85d348 completed April 10, 2026, 9:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69bb092b88190b159f1d79156cf86 completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:37 p.m.