Triple
T8696128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Cross Blue Shield Building, Boston |
E206407
|
entity |
| Predicate | facadeCharacteristic |
P30004
|
FINISHED |
| Object | sculptural façade |
—
|
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: sculptural façade | Statement: [Blue Cross Blue Shield Building, Boston, facadeCharacteristic, sculptural façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facadeCharacteristic Context triple: [Blue Cross Blue Shield Building, Boston, facadeCharacteristic, sculptural façade]
-
A.
facadeFeature
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
B.
façadeType
Indicates the specific kind or style of façade that characterizes or is applied to a building or structure.
-
C.
façadeDescription
chosen
Indicates a textual description that characterizes the appearance, style, or features of a building’s façade.
-
D.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
E.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582996a0819097ad03097ad1f103 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.