Triple
T28494151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court building at New Echota |
E721058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage site structure |
C28696
|
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: heritage site structure Context triple: [Supreme Court building at New Echota, instanceOf, heritage site structure]
-
A.
heritage site component
A heritage site component is an individual physical or spatial element within a heritage site that contributes to its overall cultural, historical, or architectural significance.
-
B.
heritage protection system element
A heritage protection system element is a component—such as a policy, structure, technology, or procedure—designed to prevent damage, loss, or degradation of cultural or natural heritage assets.
-
C.
heritage asset
chosen
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
-
D.
group of historic sites
A group of historic sites is a collection of geographically or thematically related locations that hold recognized cultural, architectural, or historical significance and are often managed or interpreted as a unified whole.
-
E.
cultural heritage monument
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.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:03 a.m.