Triple

T12582398
Position Surface form Disambiguated ID Type / Status
Subject Tyldesley E300369 entity
Predicate hasNeighbouringSettlement P4647 FINISHED
Object Astley E290982 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: Astley | Statement: [Tyldesley, hasNeighbouringSettlement, Astley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Astley
Context triple: [Tyldesley, hasNeighbouringSettlement, Astley]
  • A. Astley chosen
    Astley is a village in Greater Manchester, England, known historically for its coal mining and rural character within the Leigh area.
  • B. Astley Park
    Astley Park is a historic public park in Chorley, Lancashire, known for its landscaped grounds, woodland, and the Grade I listed Astley Hall.
  • C. Anstey
    Anstey is a large village and civil parish in Leicestershire, England, situated just northwest of Leicester and known historically for its hosiery and footwear industries.
  • D. Astley Bridge
    Astley Bridge is a suburban district and electoral ward within the town of Bolton in Greater Manchester, England.
  • E. Lankershim
    Lankershim is a surname most notably associated with Isaac Lankershim, a 19th-century landowner and developer influential in the early growth of the Los Angeles 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_69d7bde87b648190bcd0266e9efde098 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d954b97a508190b6c901c506441dd0 completed April 10, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6559c94108190834c48eb3d82ac29 completed May 2, 2026, 7:50 p.m.
Created at: April 9, 2026, 5:03 p.m.