Triple
T13905490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heaton Moor |
E334336
|
entity |
| Predicate | hasLocalCentre |
P93967
|
FINISHED |
| Object | Heaton Moor Road commercial area |
—
|
LITERAL 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: Heaton Moor Road commercial area | Statement: [Heaton Moor, hasLocalCentre, Heaton Moor Road commercial area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalCentre Context triple: [Heaton Moor, hasLocalCentre, Heaton Moor Road commercial area]
-
A.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
-
B.
hasWorldCentre
Indicates that something possesses or contains a central focal point or main hub within a particular world or global context.
-
C.
hasCenterIn
chosen
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
D.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
E.
hasCentralAxis
Indicates that one entity serves as the primary central axis or line of symmetry around which another entity is organized, aligned, or structured.
- F. None of above.
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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25dc26cc8190a7909980b1d34933 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.