Triple
T28677814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulteney Bridge, Bath |
E725916
|
entity |
| Predicate | hasShopsAlong |
P37662
|
FINISHED |
| Object | full length |
—
|
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: full length | Statement: [Pulteney Bridge, Bath, hasShopsAlong, full length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShopsAlong Context triple: [Pulteney Bridge, Bath, hasShopsAlong, full length]
-
A.
hasShopsOn
chosen
Indicates that one entity (typically a street, area, or building) contains or is lined with shops located on or along it.
-
B.
hasIndependentShops
Indicates that an entity contains or is associated with retail businesses that operate independently rather than as part of large chains or franchises.
-
C.
hasCulturalShops
Indicates that a place or area contains shops or stores that sell goods or services associated with specific cultures or cultural traditions.
-
D.
hasShop
Indicates that one entity owns, operates, or is associated with a shop or retail establishment.
-
E.
hasConfectioneryShops
Indicates that an entity operates, contains, or is associated with one or more confectionery shops.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 5:07 a.m.