Triple

T22509110
Position Surface form Disambiguated ID Type / Status
Subject Gedling district E556467 entity
Predicate hasParishes P2739 FINISHED
Object Linby 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: Linby | Statement: [Gedling district, hasParishes, Linby]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Linby
Context triple: [Gedling district, hasParishes, Linby]
  • A. Linby chosen
    Linby is a small historic village in Nottinghamshire, England, noted for its traditional stone cottages and association with the Robin Hood legend.
  • B. Brooksby
    Brooksby is a small rural village in Leicestershire, England, known for its agricultural college and historic estate.
  • C. Westhill
    Westhill is a modern commuter and service town in northeast Scotland, known particularly for its role as a hub for the offshore oil and gas industry.
  • D. Southbroom
    Southbroom is a coastal holiday village in KwaZulu-Natal, South Africa, known for its beaches, golf course, and relaxed resort atmosphere.
  • E. Grovedale
    Grovedale is a residential suburb in the southern part of Geelong, Victoria, Australia, known for its family-friendly amenities and proximity to major transport routes.
  • 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d5ebe5881908a22d519128415f2 completed April 29, 2026, 1:22 a.m.
Created at: April 16, 2026, 8:50 p.m.