Triple
T22603433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterside Plaza |
E574889
|
entity |
| Predicate | isHighRiseDevelopment |
P114769
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Waterside Plaza, isHighRiseDevelopment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighRiseDevelopment Context triple: [Waterside Plaza, isHighRiseDevelopment, true]
-
A.
isHighRise
Indicates that a building or structure is classified as a high-rise, typically due to its height exceeding a defined multi-story threshold.
-
B.
hasHighRiseBuildings
chosen
Indicates that the subject location contains one or more tall, multi-story buildings commonly classified as high-rises.
-
C.
hasHighRiseSpan
Indicates that a structure or element extends vertically across a significant number of levels or stories, forming a tall or high-rise span.
-
D.
isCondominium
Indicates that the subject property is classified or structured as a condominium.
-
E.
isRedevelopmentOf
Indicates that one entity is a newer or modified version created by redeveloping, replacing, or substantially transforming another pre-existing 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626fad6881909895cc8c0af62f0d |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:51 p.m.