Triple
T6479211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ijinkan |
E146146
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural heritage |
C3208
|
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: architectural heritage Context triple: [Ijinkan, instanceOf, architectural heritage]
-
A.
cultural heritage
Cultural heritage is the collective legacy of tangible artifacts and intangible attributes—such as traditions, languages, arts, and historical sites—passed down through generations that shape a community’s identity and values.
-
B.
cultural heritage monument
chosen
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
-
C.
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.
-
D.
design heritage
Design heritage is the enduring legacy of aesthetic principles, functional solutions, and cultural values embedded in past design practices that continue to influence and inform contemporary design.
-
E.
serial heritage property
A serial heritage property is a collection of two or more geographically separate but related heritage components that together express a single, coherent cultural or natural significance.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:51 p.m.