Triple
T17048640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop's Cleeve |
E413635
|
entity |
| Predicate | hasRetailAmenity |
P26597
|
FINISHED |
| Object | supermarkets |
—
|
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: supermarkets | Statement: [Bishop's Cleeve, hasRetailAmenity, supermarkets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailAmenity Context triple: [Bishop's Cleeve, hasRetailAmenity, supermarkets]
-
A.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
-
B.
typicalAmenity
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
-
C.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
-
D.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
E.
hasRetailPresenceIn
chosen
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa092f08190a9e37404a9de662c |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.