Triple
T7386626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heywood, Lancashire, England |
E170396
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | HEYWOOD |
E111924
|
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: HEYWOOD | Statement: [Heywood, Lancashire, England, hasPostTown, HEYWOOD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HEYWOOD Context triple: [Heywood, Lancashire, England, hasPostTown, HEYWOOD]
-
A.
Heywood
chosen
Heywood is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
-
B.
Goodshaw
Goodshaw is a village and civil parish in Lancashire, England, situated within the Borough of Rossendale.
-
C.
Holwell
Holwell is a small rural village located within the North Hertfordshire district of Hertfordshire, England.
-
D.
Harwood
Harwood is an English-language surname borne by various notable individuals across fields such as the military, arts, and politics.
-
E.
Howell
Howell is a surname and given name of Welsh origin that has been borne by numerous notable individuals across politics, sports, arts, and other fields.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f2bac481908ac74069182a4ce4 |
completed | March 27, 2026, 9:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802e56fb48190976612d2a94d6ee5 |
completed | March 28, 2026, 4:33 p.m. |
Created at: March 27, 2026, 3:08 p.m.