Triple
T5208938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Produce Exchange (consulting work) |
E117581
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical architectural activity |
C5448
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical architectural activity Context triple: [New York Produce Exchange (consulting work), instanceOf, historical architectural activity]
-
A.
architectural work
An architectural work is a designed and constructed building or structure that integrates functional, aesthetic, and technical elements to shape human environments and experiences.
-
B.
architectural district
An architectural district is a geographically defined area characterized by a concentration of buildings and structures that share significant architectural styles, historical periods, or design features, often protected or managed for their cultural and aesthetic value.
-
C.
architectural survey
chosen
An architectural survey is a systematic assessment and documentation of a building or site’s physical condition, design features, and historical or regulatory context to inform planning, preservation, or construction decisions.
-
D.
architectural association
An architectural association is a professional organization that represents, supports, and regulates the interests, standards, and development of architects and the architectural profession.
-
E.
architectural congress
An architectural congress is a formal gathering of architects, planners, scholars, and related professionals convened to discuss, present, and debate ideas, projects, and policies shaping the built environment.
- F. None of above.
Provenance (1 batch)
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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:47 p.m.