Triple

T10967089
Position Surface form Disambiguated ID Type / Status
Subject William Hulton E259128 entity
Predicate residence P75 FINISHED
Object Hulton Park E259128 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: Hulton Park | Statement: [William Hulton, residence, Hulton Park]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hulton Park
Context triple: [William Hulton, residence, Hulton Park]
  • A. Hulton Park chosen
    Hulton Park was a historic landed estate in Lancashire, England, long associated with the Hulton family and their coal-mining interests.
  • B. Oldfield Park
    Oldfield Park is a suburban area and railway station in Bath, England, serving as a local stop on the Great Western Main Line.
  • C. Baguley Park
    Baguley Park is a public green space in the Wythenshawe area of Manchester, England, offering recreational areas and natural surroundings for local residents.
  • D. Hallwood Park
    Hallwood Park is a residential area in Runcorn, Cheshire, England, forming part of the town’s New Town developments.
  • E. Haworth Park
    Haworth Park is a public recreational park in Bellevue, Nebraska, offering outdoor amenities such as green spaces, sports facilities, and riverfront access for community use.
  • 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_69d6aa88500c819097d7032ca578e74f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7714ab8588190874289f84a132fe1 completed April 9, 2026, 9:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69e3743d16ac81909c2d4eb11713512b completed April 18, 2026, 12:08 p.m.
Created at: April 8, 2026, 9:24 p.m.