Triple
T8231260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granma Memorial |
E192297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monument complex |
C10580
|
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: monument complex Context triple: [Granma Memorial, instanceOf, monument complex]
-
A.
monumental complex
chosen
A monumental complex is a large-scale, architecturally unified grouping of significant structures and spaces—such as temples, palaces, plazas, or memorials—designed to serve major ceremonial, political, religious, or commemorative functions.
-
B.
statue complex
A statue complex is an arrangement of multiple statues and related architectural elements designed as a unified spatial and thematic ensemble, often commemorating significant figures, events, or cultural narratives.
-
C.
museum building complex
A museum building complex is a coordinated group of structures and spaces designed to collect, preserve, exhibit, and interpret cultural, historical, artistic, or scientific artifacts for public education and enjoyment.
-
D.
ancient building complex
An ancient building complex is a historically significant group of interconnected or closely situated structures, often serving religious, political, residential, or commercial functions within a past civilization.
-
E.
Roman-Byzantine archaeological complex
A Roman-Byzantine archaeological complex is an integrated site containing architectural remains, artifacts, and stratified layers that document the transition and continuity between Roman and Byzantine periods in a specific region.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.