Triple
T1387505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exchange Square |
E29878
|
entity |
| Predicate | hasRetailFunction |
P23616
|
FINISHED |
| Object | high-street shops |
—
|
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: high-street shops | Statement: [Exchange Square, hasRetailFunction, high-street shops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailFunction Context triple: [Exchange Square, hasRetailFunction, high-street shops]
-
A.
hasRetailFormat
Indicates that one entity operates or is organized according to a particular retail format or store type.
-
B.
hasRetailCategory
Indicates that an entity is associated with a specific retail category or type of retail business.
-
C.
hasCommercialFunction
chosen
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
D.
hasRetailArea
Indicates that an entity possesses or includes a designated space used for retail or commercial sales activities.
-
E.
hasRetailBoutiquesIn
Indicates that an entity operates or maintains retail boutiques located within a specified place or region.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33b6e108190b6b2bca4ddd97b6c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.