Triple
T35117428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Paraíso (Peru) |
E1013480
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monumental architectural 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: monumental architectural complex Context triple: [El Paraíso (Peru), instanceOf, monumental architectural 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.
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.
-
C.
stone-built architectural complex
A stone-built architectural complex is a cohesive group of structures primarily constructed from stone, designed to function together as an integrated spatial and functional whole.
-
D.
monumental architecture
Monumental architecture is the design and construction of large-scale, often symbolically significant structures intended to convey power, identity, or collective memory within a society.
-
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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.