Triple

T6947834
Position Surface form Disambiguated ID Type / Status
Subject Bendale E160841 entity
Predicate hasNeighbouringNeighbourhood P68061 FINISHED
Object Woburn E241554 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: Woburn | Statement: [Bendale, hasNeighbouringNeighbourhood, Woburn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Woburn
Context triple: [Bendale, hasNeighbouringNeighbourhood, Woburn]
  • A. Woburn
    Woburn is a historic village in Bedfordshire, England, best known for Woburn Abbey and its associated safari park and estate.
  • B. Woburn chosen
    Woburn is a residential neighbourhood in the eastern part of Toronto, Ontario, known for its diverse community and mix of high-rise apartments and single-family homes.
  • C. Woburn, Massachusetts
    Woburn, Massachusetts is a historic suburban city north of Boston known for its early colonial roots and later prominence in industry and commerce.
  • D. Haverhill
    Haverhill is a market town in Suffolk, England, known for its growing population, light industry, and role as a commuter hub for nearby larger cities.
  • E. Haverhill
    Haverhill is a historic city in northeastern Massachusetts that functions as a suburban community within the Greater Boston metropolitan area.
  • 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_69c68850419081909fb426b8f5a304c7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1d144648190b7e6558246b013e3 completed March 27, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7753f1fe08190a734e371db4d1d38 completed March 28, 2026, 6:29 a.m.
Created at: March 27, 2026, 2:28 p.m.