Triple
T9685466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CommuniCore Plaza |
E234395
|
entity |
| Predicate | replacedAreaOf |
P29646
|
FINISHED |
| Object | former Innoventions / Future World central area |
—
|
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: former Innoventions / Future World central area | Statement: [CommuniCore Plaza, replacedAreaOf, former Innoventions / Future World central area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAreaOf Context triple: [CommuniCore Plaza, replacedAreaOf, former Innoventions / Future World central area]
-
A.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
D.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
E.
coveredArea
Indicates that one entity occupies or extends over a specific spatial region or surface area associated with another entity.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9cd0877c81909fde1989d946aae9 |
completed | April 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:16 p.m.