Triple

T2822486
Position Surface form Disambiguated ID Type / Status
Subject Batley E54841 entity
Predicate hasNeighbouringTown P3883 FINISHED
Object Morley E52490 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: Morley | Statement: [Batley, hasNeighbouringTown, Morley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morley
Context triple: [Batley, hasNeighbouringTown, Morley]
  • A. Morley chosen
    Morley is a town in West Yorkshire, England, situated between Leeds and Bradford within the Leeds City Council metropolitan area.
  • B. Heywood
    Heywood is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
  • C. Corringham
    Corringham is a small town and civil parish in the unitary authority of Thurrock in Essex, England, with historic roots and a largely residential character.
  • D. Portchester
    Portchester is a village in Hampshire, England, known for its historic Roman fort and as the birthplace of author Neil Gaiman.
  • E. Buckhaven
    Buckhaven is a coastal town in eastern Scotland, situated on the Firth of Forth in the historic county of Fife.
  • 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_69ab49e100c0819082a40cb797383243 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abde71fdc08190b18660261fe24adf completed March 7, 2026, 8:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69afceaa45e88190a9007885cf7868ef completed March 10, 2026, 7:56 a.m.
Created at: March 6, 2026, 9:59 p.m.