Triple

T2737129
Position Surface form Disambiguated ID Type / Status
Subject Holcombe Hill E60655 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Holcombe village E283911 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: Holcombe village | Statement: [Holcombe Hill, hasNearbySettlement, Holcombe village]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Holcombe village
Context triple: [Holcombe Hill, hasNearbySettlement, Holcombe village]
  • A. Holcombe chosen
    Holcombe is a village in Greater Manchester, England, known for its rural setting and proximity to the prominent Peel Monument on Holcombe Hill.
  • B. Grovehill
    Grovehill is a residential area and housing estate within the town of Hemel Hempstead in Hertfordshire, England.
  • C. Cahaba Village
    Cahaba Village is a shopping and residential development in Mountain Brook, Alabama, known for its upscale retail and dining options.
  • D. Shingletown
    Shingletown is a small rural community in Northern California known for its forested setting near Lassen Volcanic National Park.
  • E. Holt Town
    Holt Town is an inner-city area of Manchester, England, known for its industrial heritage and canalside regeneration along the River Medlock.
  • 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_69ab4b77febc819095603eb012cd141b completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdb12e03c8190b270c814ce47b626 completed March 7, 2026, 8 a.m.
NED1 Entity disambiguation (via context triple) batch_69afb6a5dda0819092508b9e10030d09 completed March 10, 2026, 6:13 a.m.
Created at: March 6, 2026, 9:56 p.m.