Triple
T13731171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Harwood |
E329800
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Blackburn |
E42839
|
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: Blackburn | Statement: [Great Harwood, near, Blackburn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blackburn Context triple: [Great Harwood, near, Blackburn]
-
A.
Blackburn
chosen
Blackburn is a large industrial town in Lancashire, England, historically known for its textile manufacturing and located north of Manchester.
-
B.
Blackburn
Blackburn is a small town in West Lothian, Scotland, known primarily as a residential community within the Central Belt.
-
C.
Blackburn Perth
The Blackburn Perth was a British biplane flying boat of the interwar period, used primarily for long-range maritime patrol and reconnaissance by the Royal Air Force.
-
D.
Bolton
Bolton is a large town in North West England known for its industrial heritage, particularly in textile manufacturing, and its location northwest of Manchester.
-
E.
Bolton
Bolton is a small town located in Hartford County in the U.S. state of Connecticut.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f92b588190be97ec4564dddd59 |
completed | April 14, 2026, 8:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d65062c819086a5f7a7ebc45412 |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.