Triple
T36891868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of America Center (Houston) |
E911765
|
entity |
| Predicate | façade |
P31596
|
FINISHED |
| Object | granite curtain wall |
—
|
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: granite curtain wall | Statement: [Bank of America Center (Houston), façade, granite curtain wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: façade Context triple: [Bank of America Center (Houston), façade, granite curtain wall]
-
A.
façadeDescription
Indicates a textual description that characterizes the appearance, style, or features of a building’s façade.
-
B.
façadeConstruction
Indicates the action or process of constructing, assembling, or installing the exterior façade of a building or structure.
-
C.
façadeDesigner
Indicates that one entity is responsible for designing the façade (external face) of a building or structure for another entity.
-
D.
façadeType
chosen
Indicates the specific kind or style of façade that characterizes or is applied to a building or structure.
-
E.
façadeSignificance
Indicates the degree of importance or meaningful role that a building’s façade has within a given context or interpretation.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd8aab0c81908a9abbf01776928a |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.