Triple
T19587642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiosk of Trajan at Philae |
E470144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian temple structure |
C3694
|
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 Egyptian temple structure Context triple: [Kiosk of Trajan at Philae, instanceOf, ancient Egyptian temple structure]
-
A.
ancient Egyptian religious architecture
Ancient Egyptian religious architecture encompasses the monumental temples, tombs, pyramids, and ritual complexes designed to honor deities, ensure pharaonic afterlife, and embody cosmic order through symbolic form, orientation, and decoration.
-
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.
ancient temple
chosen
An ancient temple is a historic sacred structure, often monumental and ornately decorated, built by past civilizations for religious worship, rituals, and offerings to deities.
-
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.
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.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.