Triple
T16782559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripylon (Central Palace) foundations |
E407891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural remains |
C27632
|
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: architectural remains Context triple: [Tripylon (Central Palace) foundations, instanceOf, architectural remains]
-
A.
ancient building
An ancient building is a historically significant structure from antiquity, often characterized by enduring construction materials, distinctive architectural styles, and cultural or archaeological importance.
-
B.
ancient structure
chosen
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.
aqueduct remains
Aqueduct remains are the surviving structural fragments of ancient water-conveyance systems, such as arches, channels, and foundations, that once transported water across landscapes.
-
D.
cathedral remains
The conceptual class "cathedral remains" represents the surviving structural elements, ruins, and archaeological traces of a once-standing cathedral, including foundations, walls, decorative fragments, and associated artifacts that indicate its former form and function.
-
E.
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.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.