Triple
T32071296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Exchange Building |
E819017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architecturally significant structure |
C28775
|
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: architecturally significant structure Context triple: [City Exchange Building, instanceOf, architecturally significant structure]
-
A.
architecturally significant building
chosen
An architecturally significant building is a structure whose design, innovation, historical importance, or cultural impact distinguishes it as notably influential or exemplary within the built environment.
-
B.
ancient structure
An ancient structure is a man-made construction from antiquity, such as temples, fortifications, or monuments, that reflects the architectural techniques, cultural values, and historical context of its originating civilization.
-
C.
heritage building complex
A heritage building complex is a group of historically or culturally significant structures and associated spaces that are preserved and managed together as a unified cultural asset.
-
D.
Manueline architectural monument
A Manueline architectural monument is a grand structure exemplifying the ornate, late-Gothic Portuguese style characterized by intricate maritime, religious, and royal symbolism carved into stone.
-
E.
commemorative structure
A commemorative structure is a built form, such as a monument or memorial, created to honor, remember, or mark a person, group, event, or idea of 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:23 a.m.