Triple
T7023189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hall Hotel, Buxton |
E162878
|
entity |
| Predicate | inTownType |
P16688
|
FINISHED |
| Object | spa town |
—
|
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: spa town | Statement: [Old Hall Hotel, Buxton, inTownType, spa town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inTownType Context triple: [Old Hall Hotel, Buxton, inTownType, spa town]
-
A.
placeType
chosen
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
B.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
C.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
D.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
E.
notableNeighborhoodType
Indicates that a neighborhood is notably characterized by, or strongly associated with, a particular type or category (e.g., residential, commercial, historic).
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.