Triple

T19662555
Position Surface form Disambiguated ID Type / Status
Subject Woodcombe E472116 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Alcombe NE NERFINISHED

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: Alcombe | Statement: [Woodcombe, hasNearbySettlement, Alcombe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alcombe
Context triple: [Woodcombe, hasNearbySettlement, Alcombe]
  • A. Alcombe chosen
    Alcombe is a residential suburb and former village now forming part of the coastal town of Minehead in Somerset, England.
  • B. Abberley
    Abberley is a rural village in Worcestershire, England, known for its historic church, scenic countryside, and the landmark Abberley Clock Tower.
  • C. Alvediston
    Alvediston is a small rural village in Wiltshire, England, known for its historic manor house and picturesque countryside setting.
  • D. Althorne
    Althorne is a small rural village and civil parish in Essex, England, situated near the River Crouch.
  • E. Cambourne
    Cambourne is a modern, rapidly growing new town in Cambridgeshire, England, developed in the late 20th century and known for its planned residential communities and local amenities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51395348190ac1416d46dfc6db0 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6414b30fc81908e6594ba8f2d2942 completed April 20, 2026, 3:07 p.m.
Created at: April 10, 2026, 1:45 p.m.