Triple

T6361349
Position Surface form Disambiguated ID Type / Status
Subject Firwood Fold E143115 entity
Predicate locatedIn P40 FINISHED
Object Bolton E38197 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: Bolton | Statement: [Firwood Fold, locatedIn, Bolton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bolton
Context triple: [Firwood Fold, locatedIn, Bolton]
  • A. 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.
  • B. Bolton
    Bolton is a small town located in Hartford County in the U.S. state of Connecticut.
  • 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 town in Ontario, Canada, serving as the main urban centre of the municipality of Bradford West Gwillimbury.
  • 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_69c008d7a9c4819098d647ec47776917 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067fa0d0c819098d01545849142fc completed March 22, 2026, 10:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c62d6d906481908b5883bff18ceec8 completed March 27, 2026, 7:10 a.m.
Created at: March 22, 2026, 4:32 p.m.