Triple
T37014086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourways Mall |
E916027
|
entity |
| Predicate | reopeningAfterExpansion |
P34772
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Fourways Mall, reopeningAfterExpansion, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopeningAfterExpansion Context triple: [Fourways Mall, reopeningAfterExpansion, 2019]
-
A.
reopeningAs
Indicates that an entity that was previously closed or inactive is starting operations again under a new or updated form, identity, or function.
-
B.
reopenedAfterCollapse
Indicates that something was closed or collapsed and then later opened or made operational again following that collapse.
-
C.
reopenedAfter
chosen
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
D.
fullyReopened
Indicates that something previously closed or partially open has been restored to complete, unrestricted operational status.
-
E.
expandedAfter
Indicates that one entity increases in size, scope, or extent after another specified event or point in time.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.