Triple

T19673539
Position Surface form Disambiguated ID Type / Status
Subject Shrewsbury–Wolverhampton line E472392 entity
Predicate servesCommunity P82 FINISHED
Object Bilbrook 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: Bilbrook | Statement: [Shrewsbury–Wolverhampton line, servesCommunity, Bilbrook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bilbrook
Context triple: [Shrewsbury–Wolverhampton line, servesCommunity, Bilbrook]
  • A. Bilbrook chosen
    Bilbrook is a village in Staffordshire, England, known as the place where geneticist Reginald Punnett died.
  • B. Hambrook
    Hambrook is a small village in South Gloucestershire, England, situated near the town of Yate and close to the city of Bristol.
  • C. Woolbrook
    Woolbrook is a small rural locality in the New England region of New South Wales, Australia.
  • D. Blackbrook
    Blackbrook is a residential area and suburb within the town of St Helens in Merseyside, England.
  • E. Purbrook
    Purbrook is a suburban village in Hampshire, England, situated near Portsmouth and forming part of the wider Havant area.
  • 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_69d8e514f2e08190ba70a4449519d218 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6416e19d881909248c4f778f7147a completed April 20, 2026, 3:08 p.m.
Created at: April 10, 2026, 1:45 p.m.