Triple
T34970654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrietta Place |
E1008528
|
entity |
| Predicate | inShoppingArea |
P120873
|
FINISHED |
| Object | Oxford Street shopping district |
—
|
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: Oxford Street shopping district | Statement: [Henrietta Place, inShoppingArea, Oxford Street shopping district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inShoppingArea Context triple: [Henrietta Place, inShoppingArea, Oxford Street shopping district]
-
A.
shoppingAccess
Indicates that an entity has the ability or opportunity to reach and use shopping facilities or retail services.
-
B.
isShoppingStreet
Indicates that a location functions primarily as a street characterized by a concentration of shops and commercial retail activity.
-
C.
isShoppingDistrict
chosen
Indicates that a location functions primarily as a shopping district, characterized by a concentration of retail stores and commercial shopping activity.
-
D.
hasShoppingMall
Indicates that one entity possesses, contains, or includes a shopping mall within its area or domain.
-
E.
isShoppingDestination
Indicates that a place serves as a primary location where people go to shop for goods or services.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.