Triple
T35194069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Sondheim Theatre |
E1016204
|
entity |
| Predicate | façadePreserved |
P173658
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Stephen Sondheim Theatre, façadePreserved, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: façadePreserved Context triple: [Stephen Sondheim Theatre, façadePreserved, yes]
-
A.
facadePreserved
chosen
Indicates that the external front or face of a structure has been maintained or kept intact, typically while other parts may have been altered or redeveloped.
-
B.
façadeDescription
Indicates a textual description that characterizes the appearance, style, or features of a building’s façade.
-
C.
façadeSignificance
Indicates the degree of importance or meaningful role that a building’s façade has within a given context or interpretation.
-
D.
façadeCommissionedBy
Indicates that the design or creation of a building’s façade was formally requested, authorized, or ordered by a specific person or organization.
-
E.
façadeConstruction
Indicates the action or process of constructing, assembling, or installing the exterior façade of a building or structure.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dccfe6c81909753fa4ff69c3fe7 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.