Triple
T22886504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bow |
E567616
|
entity |
| Predicate | energyDesignFeature |
P27882
|
FINISHED |
| Object | south-facing curved facade for solar gain |
—
|
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: south-facing curved facade for solar gain | Statement: [The Bow, energyDesignFeature, south-facing curved facade for solar gain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyDesignFeature Context triple: [The Bow, energyDesignFeature, south-facing curved facade for solar gain]
-
A.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
C.
energyEfficiencyFeature
chosen
Indicates that an entity has a design, technology, or characteristic specifically intended to reduce energy consumption or improve energy performance.
-
D.
designEnergy
Indicates that an entity is responsible for planning, specifying, or determining the energy-related characteristics or performance of another entity.
-
E.
engineeringFeature
Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fc1e3408190833a062afbea509d |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.