Triple

T22396982
Position Surface form Disambiguated ID Type / Status
Subject East Croydon E553660 entity
Predicate connectsTo P845 FINISHED
Object Bedford 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: Bedford | Statement: [East Croydon, connectsTo, Bedford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bedford
Context triple: [East Croydon, connectsTo, Bedford]
  • A. Bedford
    Bedford is a historic market town and the county town of Bedfordshire in eastern England, situated on the River Great Ouse.
  • B. Bedford
    Bedford is a small suburban city located in northeastern Ohio within the Greater Cleveland metropolitan area.
  • C. Bedford
    Bedford is an English surname of Old English origin that is also used as a place name in several English-speaking countries.
  • D. Bedford
    Bedford is a suburban community within the Halifax Regional Municipality in Nova Scotia, Canada, known for its residential areas and waterfront along the Bedford Basin.
  • E. Woburn
    Woburn is a historic village in Bedfordshire, England, best known for Woburn Abbey and its associated safari park and estate.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69e11e4da7048190b4387d422a9a0de5 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1585f67108190b8d3f23eaa0ed120 completed April 29, 2026, 1:01 a.m.
Created at: April 16, 2026, 8:45 p.m.