Triple
T7982720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackrod |
E185612
|
entity |
| Predicate | metropolitanBorough |
P15251
|
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: [Blackrod, metropolitanBorough, Bolton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bolton Context triple: [Blackrod, metropolitanBorough, 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 town in Ontario, Canada, serving as the main urban centre of the municipality of Bradford West Gwillimbury.
-
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 (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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c2a1aa881909c3cea280dff38f5 |
completed | March 31, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1c56d07481909083f028b2b5673f |
completed | April 2, 2026, 7:35 a.m. |
Created at: March 30, 2026, 5:15 p.m.