Triple

T7982781
Position Surface form Disambiguated ID Type / Status
Subject Adlington E185613 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Rivington E187559 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: Rivington | Statement: [Adlington, hasNearbySettlement, Rivington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rivington
Context triple: [Adlington, hasNearbySettlement, Rivington]
  • A. Rivington chosen
    Rivington is a rural village in Lancashire, England, known for its scenic moorland landscapes, reservoirs, and historic gardens.
  • B. Rastrick
    Rastrick is a village and residential area in West Yorkshire, England, forming part of the town of Brighouse.
  • C. Collyhurst
    Collyhurst is an inner-city district of Manchester, England, known historically for its red sandstone quarries and working-class residential character.
  • D. Ordsall
    Ordsall is an inner-city district of Salford in Greater Manchester, England, known for its historic Ordsall Hall and proximity to Manchester city centre.
  • E. Milnrow
    Milnrow is a town in Greater Manchester, England, historically part of Lancashire and known for its textile heritage and proximity to the Pennine hills.
  • 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_69ca829a2cfc819083d591d58ec04075 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c2a1aa881909c3cea280dff38f5 completed March 31, 2026, 3:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc567cfe548190bbd163a32c340bcc completed March 31, 2026, 11:19 p.m.
Created at: March 30, 2026, 5:15 p.m.