Triple
T16206695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R61 route |
E393345
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Bedford |
E124406
|
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: Bedford | Statement: [R61 route, passesThrough, Bedford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bedford Context triple: [R61 route, passesThrough, Bedford]
-
A.
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.
-
B.
Bedford
chosen
Bedford is a historic market town and the county town of Bedfordshire in eastern England, situated on the River Great Ouse.
-
C.
Bedford
Bedford is a small suburban city located in northeastern Ohio within the Greater Cleveland metropolitan area.
-
D.
Woburn
Woburn is a historic village in Bedfordshire, England, best known for Woburn Abbey and its associated safari park and estate.
-
E.
Woburn
Woburn is a residential neighbourhood in the eastern part of Toronto, Ontario, known for its diverse community and mix of high-rise apartments and single-family homes.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227101a3c819095ef40e50bf66433 |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000ed13b40819096de333872225730 |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:03 a.m.