Triple
T38225026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midas Monument inscription |
E1012118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Anatolian monument |
C56153
|
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 Anatolian monument Context triple: [Midas Monument inscription, instanceOf, ancient Anatolian monument]
-
A.
Hittite rock sanctuary
chosen
A Hittite rock sanctuary is an open-air cult site, typically carved into natural rock formations, where the Hittites conducted religious rituals, processions, and offerings to their gods.
-
B.
Hittite architectural structure
A Hittite architectural structure is a built form from the ancient Hittite civilization, typically characterized by massive stone foundations, mudbrick superstructures, fortified gateways, and orthostat reliefs integrated into palaces, temples, and city defenses.
-
C.
Akkadian monument
An Akkadian monument is a commemorative or dedicatory structure, such as a stele, statue, or inscribed stone, created by the Akkadian civilization to record political achievements, religious devotion, or historical events.
-
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.
Mycenaean funerary monument
A Mycenaean funerary monument is an architectural structure, such as a tholos tomb or chamber tomb, built by the Mycenaean civilization to honor and bury elite individuals, often featuring monumental stone construction and rich grave goods.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.