Triple
T15430440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian Labyrinth |
E369623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient architectural complex |
C4932
|
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: ancient architectural complex Context triple: [Egyptian Labyrinth, instanceOf, ancient architectural complex]
-
A.
ancient building complex
chosen
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.
-
B.
monumental complex
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.
-
C.
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.
-
D.
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.
-
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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
Created at: April 10, 2026, 3:21 a.m.