Triple
T25626905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buxton town centre conservation area |
E642457
|
entity |
| Predicate | hasKeyBuildingType |
P50464
|
FINISHED |
| Object | retail premises |
—
|
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: retail premises | Statement: [Buxton town centre conservation area, hasKeyBuildingType, retail premises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyBuildingType Context triple: [Buxton town centre conservation area, hasKeyBuildingType, retail premises]
-
A.
hasKeyBuilding
Indicates that one entity possesses or is associated with a primary or central building related to it.
-
B.
containsBuildingType
chosen
Indicates that a location or area includes at least one building of the specified type.
-
C.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
D.
belongsToBuildingType
Indicates that something is classified as being of a particular building type.
-
E.
hasBuildingClass
Indicates that a building is categorized as belonging to a specific building class or type.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 5:15 p.m.