Triple

T17391706
Position Surface form Disambiguated ID Type / Status
Subject Places for Everyone E422838 entity
Predicate appliesToRegion P82 FINISHED
Object Bolton NE NERFINISHED

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: Bolton | Statement: [Places for Everyone, appliesToRegion, Bolton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bolton
Context triple: [Places for Everyone, appliesToRegion, Bolton]
  • A. Bolton
    Bolton is a small town located in Hartford County in the U.S. state of Connecticut.
  • B. Bolton chosen
    Bolton is a large town in North West England known for its industrial heritage, particularly in textile manufacturing, and its location northwest of Manchester.
  • C. Bury
    Bury is a town in North West England known for its traditional market, historic textile industry roots, and preserved East Lancashire Railway.
  • D. Bradford
    Bradford is a major city in West Yorkshire, Northern England, known for its industrial heritage, diverse population, and role in the wool and textile industries.
  • E. Bradford
    Bradford is a masculine given name of Old English origin, traditionally meaning "broad ford" and used both as a first name and surname.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43aba5398819096846bdeefde0788 completed April 19, 2026, 2:15 a.m.
Created at: April 10, 2026, 5:45 a.m.