Triple
T12038609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasadena Cultural Heritage Landmark |
E286603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local landmark program |
C10627
|
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: local landmark program Context triple: [Pasadena Cultural Heritage Landmark, instanceOf, local landmark program]
-
A.
urban landmark
An urban landmark is a prominent, easily recognizable feature within a city—such as a building, monument, or natural formation—that serves as a visual reference point and symbol of the area’s identity.
-
B.
landmark planning blueprint
A landmark planning blueprint is a strategic, visual, and documented plan that outlines the design, placement, significance, and long-term development of key landmarks within a geographic or urban context.
-
C.
municipal program
chosen
A municipal program is an organized set of services, initiatives, or activities implemented and managed by a local government to address community needs and improve public welfare within its jurisdiction.
-
D.
community-based program
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
-
E.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.