Triple
T37971298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argyle Street (Glasgow) |
E947291
|
entity |
| Predicate | hasShoppingCentreNearby |
P127620
|
FINISHED |
| Object | St Enoch Centre |
—
|
NE NERFINISHED |
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: St Enoch Centre | Statement: [Argyle Street (Glasgow), hasShoppingCentreNearby, St Enoch Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoppingCentreNearby Context triple: [Argyle Street (Glasgow), hasShoppingCentreNearby, St Enoch Centre]
-
A.
hasShoppingDistrict
Indicates that a place contains or is associated with a designated area where multiple shops and commercial retail activities are concentrated.
-
B.
locationOfShoppingCenter
chosen
Indicates that a specified place is the geographic location where a particular shopping center is situated.
-
C.
hasShoppingMall
Indicates that one entity possesses, contains, or includes a shopping mall within its area or domain.
-
D.
hasConvenienceStore
Indicates that one entity possesses, contains, or is associated with a convenience store.
-
E.
hasShoppingDistrictType
Indicates that an entity is associated with a particular type or category of shopping district.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.