Triple
T5490716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Creek Center |
E123692
|
entity |
| Predicate | environmentalDesignFeature |
P57584
|
FINISHED |
| Object | energy-efficient systems |
—
|
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: energy-efficient systems | Statement: [City Creek Center, environmentalDesignFeature, energy-efficient systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentalDesignFeature Context triple: [City Creek Center, environmentalDesignFeature, energy-efficient systems]
-
A.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
ornamentalFeature
Indicates that one entity serves as a decorative or embellishing feature of another entity.
-
C.
featuresDecor
Indicates that one entity includes or showcases the decor elements provided or defined by another entity.
-
D.
exteriorFeature
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic of another entity.
-
E.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927f198c8190889b555be9bf9765 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a8df6481908d1643f7342fe6f0 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.