Triple
T14463367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porticus of Octavia |
E358641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monumental colonnaded 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 colonnaded complex Context triple: [Porticus of Octavia, instanceOf, monumental colonnaded 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.
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.
-
D.
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.
-
E.
ancient guesthouse complex
An ancient guesthouse complex is a historical lodging facility composed of multiple interconnected structures and courtyards designed to accommodate travelers, provide communal services, and support trade or pilgrimage along important routes.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.