Triple
T23562056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empangeni |
E579267
|
entity |
| Predicate | hasRetailFacilityType |
P4952
|
FINISHED |
| Object | shopping centres |
—
|
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: shopping centres | Statement: [Empangeni, hasRetailFacilityType, shopping centres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetailFacilityType Context triple: [Empangeni, hasRetailFacilityType, shopping centres]
-
A.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
-
B.
hasRetailStores
Indicates that an entity operates or possesses one or more physical retail store locations.
-
C.
hasRetailNetwork
Indicates that an entity operates or is associated with a system of retail outlets or distribution channels through which products or services are sold.
-
D.
hasRetailArea
Indicates that an entity possesses or includes a designated space used for retail or commercial sales activities.
-
E.
hasRetailFormat
chosen
Indicates that one entity operates or is organized according to a particular retail format or store type.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af68cddc8190ab9d0b7ee1f157ed |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:23 p.m.