Triple
T36976359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyde Park, Sandton |
E914708
|
entity |
| Predicate | shoppingFunction |
P166481
|
FINISHED |
| Object | regional shopping destination |
—
|
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: regional shopping destination | Statement: [Hyde Park, Sandton, shoppingFunction, regional shopping destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoppingFunction Context triple: [Hyde Park, Sandton, shoppingFunction, regional shopping destination]
-
A.
shoppingAccess
Indicates that an entity has the ability or opportunity to reach and use shopping facilities or retail services.
-
B.
shoppingFeature
chosen
Indicates that an entity provides or supports a shopping-related capability, option, or functionality for another entity.
-
C.
purchaseContext
Indicates the circumstances, conditions, or situational details under which a purchase occurs or is made.
-
D.
buyIn
Indicates that one party purchases or acquires an ownership stake, participation, or commitment in something initiated or owned by another party.
-
E.
shopSection
Indicates the specific section or area within a shop where an item, activity, or service is located or takes place.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.