Triple
T3488416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OL postcode area |
E73664
|
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: [OL postcode area, hasPostTown, Heywood]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heywood Context triple: [OL postcode area, hasPostTown, Heywood]
-
A.
Heywood
chosen
Heywood is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
-
B.
Morley
Morley is a town in West Yorkshire, England, situated between Leeds and Bradford within the Leeds City Council metropolitan area.
-
C.
Harwood
Harwood is an English-language surname borne by various notable individuals across fields such as the military, arts, and politics.
-
D.
Shortlands
Shortlands is a suburban area in the London Borough of Bromley, known for its residential character and commuter links into central London.
-
E.
Halstead
Halstead is a historic market town in the county of Essex in the East of England.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb92b3ac8190b8675f5a5e9d4408 |
completed | March 8, 2026, 6:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b36826ff448190880f1ee708d93215 |
completed | March 13, 2026, 1:28 a.m. |
Created at: March 8, 2026, 3:18 p.m.